Insecure deserialization In org.apache.logging.log4j:log4j
Description
JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration. The attacker can provide TopicBindingName and TopicConnectionFactoryBindingName configurations causing JMSAppender to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-44228. Note this issue only affects Log4j 1.2 when specifically configured to use JMSAppender, 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
Update Impact
Minimal update. May introduce new vulnerabilities or breaking changes.
Ecosystem | Package | Affected version | Patched versions |
|---|---|---|---|
maven | - | ||
maven | - | ||
maven | - | ||
maven | - | ||
debian 11 | 1.2.17-10+deb11u1 | ||
debian 12 | 1.2.17-11 | ||
debian 13 | 1.2.17-11 | ||
debian 14 | 1.2.17-11 | ||
rpm rhel6 | - | - | |
rpm rhel7 | 0:1.2.17-17.el7_4 |
1-10 of 13
10
Aliases
References