Vulnerability record · CVE-2017-5645 · published 17 April 2017
CVE-2017-5645: Apache Log4j 2 socket server deserialization allows remote code execution
Apache · Log4j
Apache Log4j 2.x before 2.8.2 deserializes binary log events received over its TCP or UDP socket server without validating the payload. A crafted serialized object sent to that listener can trigger arbitrary code execution. Because the socket server is a network-facing component, any reachable deployment using it is exposed.
Description
In Apache Log4j 2.x before 2.8.2, when using the TCP socket server or UDP socket server to receive serialized log events from another application, a specially crafted binary payload can be sent that, when deserialized, can execute arbitrary code.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Automated analysis
critical priorityCVSS 9.8 with no authentication or user interaction required, and a very high EPSS score, make this a high-impact remote code execution flaw.
What it is
Apache Log4j 2.x before 2.8.2 deserializes binary log events received over its TCP or UDP socket server without validating the payload. A crafted serialized object sent to that listener can trigger arbitrary code execution. Because the socket server is a network-facing component, any reachable deployment using it is exposed.
Impact
An unauthenticated remote attacker can execute arbitrary code with the privileges of the Log4j process, leading to full host compromise. This can result in data theft, lateral movement, or service disruption.
Attack surface
Reached over the network via the Log4j TCP or UDP socket server listener; the CVSS vector shows no privileges or user interaction required. Exploitation requires the socket server to be enabled and reachable by the attacker.
Exploitation
Not listed in CISA KEV and no ransomware associations are documented, but EPSS is very high (0.89792, 99.78th percentile), indicating substantial predicted exploitation activity. References are patch advisories and third-party advisories, with no public exploit tag supplied.
What to do
- Upgrade Apache Log4j 2.x to 2.8.2 or later, and apply vendor patches for affected Oracle, Red Hat, and NetApp products.
- Disable the Log4j TCP and UDP socket server listeners where they are not strictly required.
- Restrict network access to any Log4j socket server port to trusted hosts only, using firewall or segmentation controls.
- If the socket server must remain enabled, use a Java deserialization filter or allowlist to block untrusted classes.
- Inventory applications and embedded dependencies for bundled Log4j 2.x versions and track remediation.
Detection
- Monitor network traffic to Log4j socket server ports for unexpected or anomalous serialized payloads.
- Alert on Log4j process spawning child processes or making outbound connections it does not normally make.
- Search logs for deserialization errors or exceptions from the Log4j socket server component.
- Use file integrity monitoring and endpoint detection to catch post-exploitation activity on hosts running Log4j 2.x.
This assessment is produced automatically and is not human-reviewed. Verify against the vendor advisory before acting on it.
Affected products
79 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
Track CVE-2017-5645 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2017-5645), CISA KEV, FIRST EPSS (scores of 2026-09-26). This page is refreshed as NVD updates the record.