CONTENTUM.COMA specialist. A plan. A result.

Vulnerabilities · 2022 · Apache

CVE-2022-23302
Apache Log4j vulnerability

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.

Affected products

Log4j, Snapmanager, Brocade Sannav, Reload4j, Advanced Supply Chain Planning, Business Intelligence, Business Process Management Suite, Communications Eagle Ftp Table Base Retrieval, Communications Instant Messaging Server, Communications Messaging Server and more. The exact versions are in the references.

What to do now

  • Check your exposureFind out whether Apache Log4j runs anywhere in your environment, including systems of suppliers.
  • UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
  • Set the orderSystems that can be reached from the internet come first, then the rest.

References

More vulnerabilities in Apache products

Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.