Red Hat: CVE-2022-23302: CVE-2022-23302 log4j: Remote code execution in Log4j 1.x when application is configured to use JMSSink (Multiple Advisories)
Description
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.
Solution(s)
- redhat-upgrade-log4j
- redhat-upgrade-log4j-debuginfo
- redhat-upgrade-log4j-javadoc
- redhat-upgrade-log4j-manual
- redhat-upgrade-parfait
- redhat-upgrade-parfait-examples
- redhat-upgrade-parfait-javadoc
- redhat-upgrade-pcp-parfait-agent
- redhat-upgrade-si-units
- redhat-upgrade-si-units-javadoc
- redhat-upgrade-unit-api
- redhat-upgrade-unit-api-javadoc
- redhat-upgrade-uom-lib
- redhat-upgrade-uom-lib-javadoc
- redhat-upgrade-uom-parent
- redhat-upgrade-uom-se
- redhat-upgrade-uom-se-javadoc
- redhat-upgrade-uom-systems
- redhat-upgrade-uom-systems-javadoc
- Lightweight Endpoint Agent
- Live Dashboards
- Real Risk Prioritization
- IT-Integrated Remediation Projects
- Cloud, Virtual, and Container Assessment
- Integrated Threat Feeds
- Easy-to-Use RESTful API
- Automation-Assisted Patching
- Automated Containment
With Rapid7 live dashboards, I have a clear view of all the assets on my network, which ones can be exploited, and what I need to do in order to reduce the risk in my environment in real-time. No other tool gives us that kind of value and insight.
– Scott Cheney, Manager of Information Security, Sierra View Medical Center