CVE-2022-23302
high-risk
Published 2022-01-18
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.
Do I need to act?
-
0.65% chance of exploitation
EPSS score — low exploit probability
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
8
CVSS 8.8/10
High
NETWORK
/ LOW complexity
Affected Products (20)
Reload4J
Advanced Supply Chain Planning
Advanced Supply Chain Planning
References (14)
Vendor Advisory
https://logging.apache.org/log4j/1.2/index.html
Third Party Advisory
https://security.netapp.com/advisory/ntap-20220217-0006/
Vendor Advisory
https://logging.apache.org/log4j/1.2/index.html
Third Party Advisory
https://security.netapp.com/advisory/ntap-20220217-0006/
56
/ 100
high-risk
Severity
30/34 · Critical
Exploitability
2/34 · Minimal
Exposure
24/34 · High