Skip to main content
Public proof of conceptFix available

CVE-2021-4104

A public proof of concept exists; no exploitation attested.

  • Published2021-12-14
  • WeaknessCWE-502

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration. The attacker can provide TopicBindingName and TopicConnectionFactoryBindingName configurations causing JMSAppender to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-44228. Note this issue only affects Log4j 1.2 when specifically configured to use JMSAppender, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.

Timeline

dates in UTC
  1. 2021-12-1412:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-11-03 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2021-4104?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2021-4104?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Apache Log4j
BranchAffectedFixed in
1.2= 1.2no fix published
Oracle communications unified inventory management
BranchAffectedFixed in
7.3= 7.3.4no fix published
7.3= 7.3.5no fix published
7.4= 7.4.1no fix published
7.4= 7.4.2no fix published
Oracle retail allocation
BranchAffectedFixed in
14.1= 14.1.3.2no fix published
15.0= 15.0.3.1no fix published
16.0= 16.0.3no fix published
19.0= 19.0.1no fix published

45 more products in the sources.

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As apache, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Apache Software Foundation Apache Log4j 1.x
    Affected
    • = Apache Log4j 1.2 1.2.xno fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2023-12-22

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • apache-druidMinimOSall versions · fixed in 0and 1 other package
  • apache-hiveCleanStartall versions · fixed in 3.1.3-r1
  • apache-log4j1.2Ubuntu:Pro:16.04:LTSall versions · fixed in 1.2.17-7ubuntu1+esm1
  • apache-log4j1.2Ubuntu:Pro:14.04:LTSall versions · fixed in 1.2.17-4ubuntu3+esm1
  • apache-log4j1.2Ubuntu:20.04:LTSall versions · fixed in 1.2.17-9ubuntu0.1
  • apache-log4j1.2Ubuntu:18.04:LTSall versions · fixed in 1.2.17-8+deb10u1ubuntu0.1
  • apache-log4j1.2Debian:14all versions · fixed in 1.2.17-11
  • apache-log4j1.2Debian:13all versions · fixed in 1.2.17-11

416 more package ranges on OSV.dev

Vendor advisories

  • CVE-2021-4104 Red Hat Product Security579 products fixed · 7 known affected

    log4j: Remote code execution in Log4j 1.x when application is configured to use JMSAppender

    log4j.src as a component of A-MQ Clients 2 · log4j.src as a component of Red Hat AMQ Broker 7 · log4j.src as a component of Red Hat JBoss Fuse Service Works 6 · +4 more

  • RHSA-2024:10207 Red Hat Product Security59 products fixed

    Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 7.3.11 Security update

  • RHSA-2024:5856 Red Hat Product Security2 products fixed

    Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 7.1.7 on RHEL 7 security update

  • RHSA-2022:5460 Red Hat Product Security130 products fixed

    Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 6.4.24 security update

  • RHSA-2022:5459 Red Hat Product Security130 products fixed

    Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 6.4.24 security update

  • RHSA-2022:5458 Red Hat Product Security1 product fixed

    Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 6.4.24 security update

34 more advisories

Full record on NVD

Fix

  1. Vendor fix Red Hat Product Security RHSA-2024:10207 · 59 productsBefore applying this update, ensure all previously released errata relevant to your system have been applied. Also, back up your existing installation, including all applications, configuration files, databases and database settings. For details on how to apply this update, refer to: https://access…
  2. Vendor fix Red Hat Product Security RHSA-2022:5460 · 130 productsBefore applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
  3. Vendor fix Red Hat Product Security RHSA-2022:5459 · 130 productsBefore applying this update, back up your existing Red Hat JBoss Enterprise Application Platform installation and deployed applications. For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
  4. Vendor fix Red Hat Product Security RHSA-2022:5458 · 1 productBefore applying this update, back up your existing Red Hat JBoss Enterprise Application Platform installation and deployed applications. The References section of this erratum contains a download link (you must log in to download the update).
  5. Vendor fix Red Hat Product Security RHSA-2022:0661 · 1 productBefore applying the update, back up your existing installation, including all applications, configuration files, databases and database settings, and so on. Installation instructions are available from the Fuse 7.10 product documentation page: https://access.redhat.com/documentation/en-us/red_hat_…
  6. Vendor fix Red Hat Product Security RHSA-2022:0553 · 1 productBefore applying the update, back up your existing installation, including all applications, configuration files, databases and database settings, and so on. Installation instructions are located in the download section of the customer portal. The References section of this erratum contains a down…

Detection

read 2026-11-03 22:42 UTC
Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
3 repositories, unverifiedcckuailong/log4shell_1.xopen-AIMS/log4jcuijiung/log4j-CVE-2021-4104
PoC-in-GitHub
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Published
2021-12-14
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-fp5r-v3w9-4333

Frequently asked questions

What is CVE-2021-4104?

JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration. The attacker can provide TopicBindingName and TopicConnectionFactoryBindingName configurations causing JMSAppender to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-44228. Note this issue only affects Log4j 1.2 when specifically configured to use JMSAppender, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.

Is CVE-2021-4104 actively exploited?

Active exploitation of CVE-2021-4104 has not been confirmed. Its EPSS score was 80.6% on 2026-11-03, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2021-4104?

CVE-2021-4104 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H.

Running Apache Log4j? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record