Deserialization of Untrusted Data The advisory has been revoked - it doesn't affect any version of package tomcat-jsvc  (opens in a new tab)


Threat Intelligence

EPSS
63.84% (100th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CENTOS7-TOMCATJSVC-2347473
  • published19 Jan 2022
  • disclosed18 Jan 2022

Introduced: 18 Jan 2022

CVE-2022-23302  (opens in a new tab)
CWE-502  (opens in a new tab)

Amendment

The Centos security team deemed this advisory irrelevant for Centos:7.

NVD Description

Note: Versions mentioned in the description apply only to the upstream tomcat-jsvc package and not the tomcat-jsvc package as distributed by Centos.

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.