Loading vulnerability…
CVE-2019-17571 is an unsafe deserialization vulnerability in the SocketServer class of Apache Log4j 1.2, affecting releases through 1.2.17. SocketServer accepts serialized log events and deserializes them without enforcing an allowlist of permitted object types. An attacker can supply a malicious serialized object that invokes a suitable deserialization gadget chain during object reconstruction, resulting in arbitrary code execution. This issue is distinct from CVE-2017-5645, which affects analogous socket-server functionality in Log4j 2.x.
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 valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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 code injection vulnerability affecting SAP Quotation Management Insurance application (FS-QUO).
Unauthenticated remote code execution via insecure deserialization in an embedded/outdated Apache Log4j SocketServer component within SAP FS-QUO 800, potentially leading to complete system compromise.
Deserialization of untrusted data vulnerability in the Log4j 1.x SocketServer component.
An Apache Log4j 1.x deserialization-of-untrusted-data vulnerability in SocketServer. The Red Hat JBoss Data Virtualization service pack mitigates the referenced Log4j issues by removing affected classes.
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.