VDB

CVE-2021-4104

CVE-2021-4104 PUBLISHED CVSS 7.5 HIGH

Deserialization of untrusted data in JMSAppender in Apache Log4j 1.2

Reported by apache · Published December 14, 2021

log4j-1.2.17 is fixed in 2.0 (Maven Central)

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.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
org.zenframework.z8.dependencies.commons:log4j-1.2.17Maven Central2.0
log4j:log4jMaven Central1.2.17
log4jAmazon Linux1.2.17-17.amzn2
log4j-manualAmazon Linux1.2.17-17.amzn2
druidChainguard35.0.1-r1
log4j-javadocAmazon Linux1.2.17-17.amzn2
druidWolfi35.0.1-r1
mysql_enterprise_monitororacle8.0.29
hyperion_infrastructure_technologyoracle11.2.8.0
communications_offline_mediation_controlleroracle12.0.0.4.0
hyperion_data_relationship_managementoracle11.2.8.0

Risk scores

CVSS 3.1
7.5
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

VendorProductVersions
Apache Software FoundationApache Log4j 1.xApache Log4j 1.2 1.2.x
Mavenorg.apache.logging.log4j:log4j-core1.2
Mavenorg.zenframework.z8.dependencies.commons:log4j-1.2.170
amazon:2log4j0
Mavenorg.apache.logging.log4j:log4j1.2
amazon:2log4j-manual0
chainguarddruid0
amazon:2log4j-javadoc0
wolfidruid0
Mavenlog4j:log4j1.2
Apache Software FoundationApache Log4j 1.x1.2

Timeline

  • Dec 13, 2021 PoC Published (17 in total, the first dated here)
  • Dec 14, 2021 CVE Published
  • Dec 14, 2021 VulnCheck XDB Entry
  • Dec 15, 2021 EPSS Score (30 in total, the first dated here)
  • Apr 26, 2022 VulnCheck KEV Exploitation (4 in total, the first dated here)
  • Mar 17, 2026 Security Advisory (60 in total, the first dated here)
  • Apr 1, 2026 Distribution Patch (48 in total, the first dated here)
  • Jul 21, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2021-4104
vulnetix vdb fixes CVE-2021-4104

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2021-4104/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›