Deserialization of untrusted data in JMSSink in Apache Log4j 1.x
CVE-2022-23302

8.8HIGH

Key Information:

Vendor
Apache
Status
Apache Log4j 1.x
Vendor
CVE Published:
18 January 2022

Summary

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.

Affected Version(s)

Apache Log4j 1.x 1.0.1

Apache Log4j 1.x < 2.0-alpha1

References

https://lists.apache.org/thread/bsr3l5qz4g0myrjhy9h67bcxo...
x_refsource_MISC
https://logging.apache.org/log4j/1.2/index.html
x_refsource_MISC
http://www.openwall.com/lists/oss-security/2022/01/18/3
mailing-listx_refsource_MLIST

EPSS Score

7% chance of being exploited in the next 30 days.

CVSS V3.1

Score:
8.8
Severity:
HIGH
Confidentiality:
High
Integrity:
High
Availability:
High
Attack Vector:
Network
Attack Complexity:
Low
Privileges Required:
Low
User Interaction:
None
Scope:
Unchanged

Timeline

  • Vulnerability published

  • Vulnerability Reserved

Credit

Eduardo' Vela, Maksim Shudrak and Jacob Butler from Google.
.