Quick answers
- Is CVE-2019-17571 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2019-17571 being exploited in the wild.
- How severe is CVE-2019-17571?
- Critical severity, with a CVSS score of 9.8, published 6 January 2020.
- Which products and versions are affected?
- Apache Log4j >= 1.2, <= 1.2.17; log4j:log4j (Maven) >= 1.2, <= 1.2.17, ECOSYSTEM:introduced=1.2,last_affected=1.2.17; org.zenframework.z8.dependencies.commons:log4j-1.2.17 (Maven) = 2.0.
- Is there a fix for CVE-2019-17571?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2019-17571 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2019-17571?
- Check whether you run Apache Log4j, log4j:log4j (Maven) or org.zenframework.z8.dependencies.commons:log4j-1.2.17 (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The SocketServer class in Apache Log4j versions 1.2 through 1.2.17 is vulnerable to deserialization of untrusted data. When the SocketServer is configured to listen for log data on a network port, it fails to properly validate incoming serialized objects. A remote, unauthenticated attacker can send a specially crafted malicious payload that, when combined with a suitable deserialization gadget on the classpath, results in arbitrary code execution. No patch is available for the 1.2.x branch as it has reached end-of-life; users must migrate to log4j-core (Log4j 2.x).
Affected products
- Apache Log4j >= 1.2, <= 1.2.17
Identifiers
- CVE-2019-17571
- GHSA-2qrg-x229-3v8q
Timeline
- 2020-01-06: advisory: GitHub Advisory published