CVE-2021-4104
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.
| Package | Ecosystem | Fixed in |
|---|---|---|
| org.zenframework.z8.dependencies.commons:log4j-1.2.17 | Maven Central | 2.0 |
| log4j:log4j | Maven Central | 1.2.17 |
| log4j | Amazon Linux | 1.2.17-17.amzn2 |
| log4j-manual | Amazon Linux | 1.2.17-17.amzn2 |
| druid | Chainguard | 35.0.1-r1 |
| log4j-javadoc | Amazon Linux | 1.2.17-17.amzn2 |
| druid | Wolfi | 35.0.1-r1 |
| mysql_enterprise_monitor | oracle | 8.0.29 |
| hyperion_infrastructure_technology | oracle | 11.2.8.0 |
| communications_offline_mediation_controller | oracle | 12.0.0.4.0 |
| hyperion_data_relationship_management | oracle | 11.2.8.0 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Apache Software Foundation | Apache Log4j 1.x | Apache Log4j 1.2 1.2.x |
| Maven | org.apache.logging.log4j:log4j-core | 1.2 |
| Maven | org.zenframework.z8.dependencies.commons:log4j-1.2.17 | 0 |
| amazon:2 | log4j | 0 |
| Maven | org.apache.logging.log4j:log4j | 1.2 |
| amazon:2 | log4j-manual | 0 |
| chainguard | druid | 0 |
| amazon:2 | log4j-javadoc | 0 |
| wolfi | druid | 0 |
| Maven | log4j:log4j | 1.2 |
| Apache Software Foundation | Apache Log4j 1.x | 1.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
References
- VU#930724 third-party-advisory
- [oss-security] 20220118 CVE-2022-23302: Deserialization of untrusted data in JMSSink in Apache Log4j 1.x mailing-list
- GLSA-202209-02 vendor-advisory
- GLSA-202310-16 vendor-advisory
- GLSA-202312-02 vendor-advisory
- GLSA-202312-04 vendor-advisory
- [MaJ] Vulnérabilité dans Apache Log4j advisory
- https://nvd.nist.gov/vuln/detail/CVE-2021-4104 advisory
- https://github.com/advisories/GHSA-fp5r-v3w9-4333 advisory