Loading vulnerability…
CVE-2022-23302 is a deserialization-of-untrusted-data vulnerability in the JMSSink component of Apache Log4j 1.x. In Log4j deployments specifically configured to use JMSSink, an attacker able to modify the Log4j configuration, or to influence an LDAP service referenced by that configuration, can supply a malicious TopicConnectionFactoryBindingName value. JMSSink then performs JNDI requests that can result in remote code execution. JMSSink is not enabled by default. Log4j 1.x, including Log4j 1.2, is end of life and no longer maintained.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
48 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A remote-code-execution vulnerability in Apache Log4j 1.x applications configured to use JMSSink.
A high-severity deserialization-of-untrusted-data vulnerability in Apache Log4j 1.x JMSSink. Under non-default configurations that use JMSSink, an attacker able to modify Log4j configuration or control a referenced LDAP service can cause JNDI requests and potentially achieve remote code execution.
A vulnerability tracked as CVE-2022-23302, addressed by a Unity Linux security update (UTSA-2026-093022). The provided CVSS v3 vector indicates network attack surface, low attack complexity, low-privileged access required, no user interaction, and high confidentiality, integrity, and availability impact.
Remote-code-execution vulnerability in Log4j 1.x when an application is configured to use JMSSink.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.