● CVE — High
CVE-2022-23302
Vendororacle, netapp, broadcom, apache, qosProductbusiness intelligence, jdeveloper, communications unified inventory management, snapmanager, hyperion data relationship management, business process management suite, healthcare foundation, communications instant messaging server, enterprise manager base platform, communications network integrity, mysql enterprise monitor, identity manager connector, tuxedo, communications messaging server, hyperion infrastructure technology, financial services revenue management and billing analytics, brocade sannav, communications offline mediation controller, middleware common libraries and tools, advanced supply chain planning, log4j, reload4j, communications eagle ftp table base retrieval, e-business suite cloud manager and cloud backup module, identity management suiteDiscoveredJan 18, 2022UpdatedJul 7, 2025
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.