[<prev] [next>] [day] [month] [year] [list]
Message-ID: <5f9df975-a7a3-a9c8-28b1-4331ab9b66c6@apache.org>
Date: Tue, 18 Jan 2022 14:42:17 +0000
From: Ralph Goers <rgoers@...che.org>
To: oss-security@...ts.openwall.com
Subject: CVE-2022-23302: Deserialization of untrusted data in JMSSink in
Apache Log4j 1.x
Severity: high
Description:
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.
Mitigation:
Users should upgrade to Log4j 2 or remove usage of the JMSSink from their configurations.
Credit:
Eduardo' Vela, Maksim Shudrak and Jacob Butler from Google.
Powered by blists - more mailing lists
Please check out the
Open Source Software Security Wiki, which is counterpart to this
mailing list.
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
