Deserialization in Apache Log4j

CVE-2022-23302

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.

Vulnerability class: Insecure Deserialization

EPSS: 0.636 (99.2th percentile) — read the EPSS interpretation.

CVSS v3 metric

CVSS v3 base score 8.8 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Affected products

Weakness classification (CWE)

Public proof-of-concept exploits

References

Frequently asked questions

What is CVE-2022-23302?
CVE-2022-23302 is a high-severity vulnerability in Apache Log4j, classified under Deserialization of Untrusted Data. CVSS score: 8.8/10. Published 2022-01-18.
How severe is CVE-2022-23302?
High severity. CVSS v3 base score is 8.8 out of 10.
Is CVE-2022-23302 known to be exploited?
18 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.