CVE-2022-23302
Deserialization of untrusted data in JMSSink in Apache Log4j 1.x
Reported by apache · Published January 18, 2022
log4j-1.2.17 is fixed in 2.0 (Maven Central)
JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-4104. Note this issue only affects Log4j 1.x when specifically configured to use JMSSink, 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-javadoc | Amazon Linux | 1.2.17-18.amzn2 |
| druid | Wolfi | 35.0.1-r1 |
| druid | Chainguard | 35.0.1-r1 |
| log4j-manual | Amazon Linux | 1.2.17-18.amzn2 |
| log4j | Amazon Linux | 1.2.17-18.amzn2 |
| hyperion_infrastructure_technology | oracle | 11.2.8.0 |
| e-business_suite_cloud_manager_and_cloud_backup_module | oracle | 2.2.1.1.1 |
| log4j | apache | 1.2.17 |
| communications_offline_mediation_controller | oracle | 12.0.0.4.4 |
| reload4j | qos | 1.2.18.1 |
3 more packages have a fixed version. See every fix in Lookup.
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Apache Software Foundation | Apache Log4j 1.x | 1.0.1, unspecified |
| apache | log4j | |
| Maven | org.zenframework.z8.dependencies.commons:log4j-1.2.17 | 0 |
| Maven | log4j:log4j | 0 |
| amazon:2 | log4j-javadoc | 0 |
| wolfi | druid | 0 |
| Apache Software Foundation | Apache Log4j 1.x | 1.0.1, * |
| chainguard | druid | 0 |
| amazon:2 | log4j-manual | 0 |
| amazon:2 | log4j | 0 |
Timeline
- Jan 17, 2022 CVE Published
- Feb 8, 2022 EPSS Score (30 in total, the first dated here)
- Mar 17, 2026 Security Advisory (42 in total, the first dated here)
- Jul 5, 2026 Coalition ESS Score
- Nov 21, 2026 Distribution Patch (37 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2022-23302
vulnetix vdb fixes CVE-2022-23302
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-2022-23302/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart
References
- x_refsource_MISC
- x_refsource_MISC
- [oss-security] 20220118 CVE-2022-23302: Deserialization of untrusted data in JMSSink in Apache Log4j 1.x mailing-listx_refsource_MLIST
- x_refsource_MISC
- x_refsource_CONFIRM
- x_refsource_MISC
- https://nvd.nist.gov/vuln/detail/CVE-2022-23302 advisory
- https://github.com/advisories/GHSA-w9p3-5cr8-m3jj advisory
- https://github.com/apache/logging-log4j1 url
- https://security.netapp.com/advisory/ntap-20220217-0006 advisory
- https://www.vicarius.io/vsociety/posts/cve-2022-23302-detect-log4j-1217-vulnerability url
- https://www.vicarius.io/vsociety/posts/cve-2022-23302-mitigate-log4j-1217-vulnerability url