Skip to main content
Mallory
CriticalVulnerability

CVE-2019-17571: Remote Code Execution in Apache Log4j 1.2 SocketServer

Published Dec 20, 2019 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS70.0%99th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendors
Oracle CorporationApache Software FoundationDebian ProjectNetAppOpensuseCanonical
IdentifiersCVE-2019-17571CWE-502 · Deserialization of Untrusted Data

CVE-2019-17571 is an unsafe deserialization vulnerability in the SocketServer class of Apache Log4j 1.2 through 1.2.17. SocketServer accepts serialized log events from network clients and deserializes them without verifying that the objects are permitted. An unauthenticated remote attacker can supply crafted serialized data to execute arbitrary code when the receiving application has a usable deserialization gadget chain. The vulnerability requires the affected socket-server functionality to process untrusted network traffic; merely including Log4j does not establish exploitability. This issue is distinct from the analogous Log4j 2.x vulnerability CVE-2017-5645.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can execute arbitrary code with the privileges of the application running SocketServer, potentially compromising the confidentiality, integrity, and availability of data and services accessible to that process. Outcomes can include sensitive-data access, unauthorized modification, and service disruption. Operating-system privilege escalation is not an inherent consequence.

Mitigation

If you can’t patch tonight, do this now.

Disable the affected SocketServer functionality or remove its class if it is not required. If immediate removal or migration is not possible, prevent untrusted sources from reaching the logging listener using firewall rules and network segmentation, limiting access to trusted log senders. Network restrictions reduce exposure but do not eliminate the unsafe deserialization behavior.

Remediation

Patch, then assume compromise.

Replace end-of-life Log4j 1.x dependencies with a currently supported, patched Log4j 2 release and migrate the affected logging configuration. Apache Log4j 1.x reached end of life in August 2015 and has no upstream fixed release for this issue. For vendor-maintained distributions, apply the applicable vendor security update containing a backported fix; examples include RHEL 6 ELS log4j 1.2.14-6.7.el6_10 under RHSA-2022:5053 and RHEL 7 log4j 1.2.17-16.el7_4 under RHSA-2017:2423. Evaluate vendor patch status rather than relying solely on the upstream version number.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
Every candidate exploit was rejected by Mallory's analysis.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Apache Software FoundationBookkeeperapplication
Apache Software FoundationLog4japplication
CanonicalUbuntu Linuxoperating_system
Debian ProjectDebian Linuxoperating_system
NetAppOncommand System Managerapplication
NetAppOncommand Workflow Automationapplication
OpensuseOpensuse Leapoperating_system
Oracle CorporationApplication Testing Suiteapplication
Oracle CorporationCommunications Network Integrityapplication
Oracle CorporationEndeca Information Discovery Studioapplication
Oracle CorporationFinancial Services Lending And Leasingapplication
Oracle CorporationMysql Enterprise Monitorapplication
Oracle CorporationOracle Weblogic Serverapplication
Oracle CorporationPrimavera Gatewayapplication
Oracle CorporationRapid Planningapplication
Oracle CorporationRetail Extract Transform And Loadapplication
Oracle CorporationRetail Service Backboneapplication
FAQ

Frequently asked questions

Is CVE-2019-17571 exploited in the wild?
As of Oct 17, 2026, Mallory has no reports of CVE-2019-17571 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2019-17571?
As of Oct 17, 2026, Mallory has found no public exploit for CVE-2019-17571.
Is there a patch for CVE-2019-17571?
Replace end-of-life Log4j 1.x dependencies with a currently supported, patched Log4j 2 release and migrate the affected logging configuration. Apache Log4j 1.x reached end of life in August 2015 and has no upstream fixed release for this issue.
What products are affected by CVE-2019-17571?
Apache Software Foundation Log4j, Oracle Corporation Application Testing Suite, Apache Software Foundation Bookkeeper, Oracle Corporation Communications Network Integrity, Debian Project Debian Linux, and 12 more.
How severe is CVE-2019-17571?
CVE-2019-17571 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 70.0% (99th percentile) as of Oct 17, 2026.
Activity feed

Recent activity

52 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+24 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity10Community discussion across Reddit, Mastodon, and other social sources.