CVE-2022-23307
Deserialization of Untrusted Data in Apache Log4j
Reported by apache · Published January 18, 2022
log4j is fixed in 2.0 and 1.2.17 (Maven Central)
CVE-2020-9493 identified a deserialization issue that was present in Apache Chainsaw. Prior to Chainsaw V2.0 Chainsaw was a component of Apache Log4j 1.2.x where the same issue exists.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| log4j:log4j | Maven Central | 2.0, 1.2.17 |
| org.apache.logging.log4j:log4j | Maven Central | 2.0 |
| org.zenframework.z8.dependencies.commons:log4j-1.2.17 | Maven Central | 2.0 |
| log4j-javadoc | Amazon Linux | 1.2.17-18.amzn2 |
| log4j | Amazon Linux | 1.2.17-18.amzn2 |
| log4j-manual | Amazon Linux | 1.2.17-18.amzn2 |
| druid | Chainguard | 35.0.1-r1 |
| druid | Wolfi | 35.0.1-r1 |
| Apache Log4j 1.x | Apache Software Foundation | unspecified, 2.0-alpha1 |
| log4j | apache | 2.0 |
| mysql_enterprise_monitor | oracle | 8.0.29 |
| reload4j | qos | 1.2.18.1 |
5 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.2.1, unspecified |
| Apache Software Foundation | Apache Log4j 1.x | *, 1.2.1 |
| Maven | org.webjars.npm:chainsaw | 0 |
| amazon:2 | log4j-javadoc | 0 |
| Maven | org.apache.logging.log4j:log4j | 1.2 |
| amazon:2 | log4j | 0 |
| amazon:2 | log4j-manual | 0 |
| Maven | org.zenframework.z8.dependencies.commons:log4j-1.2.17 | 0 |
| chainguard | druid | 0 |
| Maven | log4j:log4j | 1.2 |
| wolfi | druid | 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
- Sep 20, 2026 CVE Updated
- 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-23307
vulnetix vdb fixes CVE-2022-23307
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-23307/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
- x_refsource_MISC
- x_refsource_MISC
- https://nvd.nist.gov/vuln/detail/CVE-2022-23307 advisory
- https://github.com/advisories/GHSA-f7vh-qwp3-x37m advisory