JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data
GHSA-fp5r-v3w9-4333 · CVE-2021-4104
Published · Modified
AI SAST
Find this class of vulnerability in your own code
Corgea's AI-native static analysis detects vulnerabilities like this one across your repositories, ranks them by exploitability, and returns review-ready fixes.
Description
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.
References
- ADVISORY https://nvd.nist.gov/vuln/detail/CVE-2021-4104
- WEB https://github.com/apache/logging-log4j2/pull/608#issuecomment-990494126
- WEB https://access.redhat.com/security/cve/CVE-2021-4104
- PACKAGE https://github.com/apache/logging-log4j2
- WEB https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2021-0033
- WEB https://security.gentoo.org/glsa/202209-02
- WEB https://security.gentoo.org/glsa/202310-16
- WEB https://security.gentoo.org/glsa/202312-02
- WEB https://security.gentoo.org/glsa/202312-04
- WEB https://security.netapp.com/advisory/ntap-20211223-0007
- WEB https://www.cve.org/CVERecord?id=CVE-2021-44228
- WEB https://www.kb.cert.org/vuls/id/930724
- WEB https://www.oracle.com/security-alerts/cpuapr2022.html
- WEB https://www.oracle.com/security-alerts/cpujan2022.html
- WEB https://www.oracle.com/security-alerts/cpujul2022.html
- WEB http://www.openwall.com/lists/oss-security/2022/01/18/3
Ready to move
Start Securing
Free, no credit card | First findings in minutes