First published: Tue Jan 18 2022(Updated: )
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 <a href="https://access.redhat.com/security/cve/CVE-2021-4104">CVE-2021-4104</a>. Note this issue only affects Log4j 1.x when specifically configured to use JMSSink, which is not the default. References: <a href="https://www.openwall.com/lists/oss-security/2022/01/18/3">https://www.openwall.com/lists/oss-security/2022/01/18/3</a>
Affected Software | Affected Version | How to fix |
---|---|---|
Apache Log4j | <=1.x |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-2041949 is high due to the potential for remote code execution through deserialization vulnerabilities.
To fix REDHAT-BUG-2041949, update to a supported version of Log4j that is not affected by this vulnerability.
REDHAT-BUG-2041949 affects all versions of Log4j 1.x.
If you have write access to the Log4j configuration, ensure it does not reference any untrusted LDAP services to mitigate the risk of exploitation associated with REDHAT-BUG-2041949.
Yes, there are known exploitation techniques that leverage the deserialization vulnerability in REDHAT-BUG-2041949.