Skip to main content

Over 150 LLM Providers · Over 5,300 Models The most extensible AI-powered pentesting platform. Open source. Star on GitHub

CVE-2019-17571

9.8 · CRITICAL
Published Dec 20, 2019 apache CWE-502 EPSS 69.06% (99th pctl)

Overview

CVE-2019-17571 is a critical-severity vulnerability affecting apache log4j. It was published on December 20, 2019 and has a CVSS 3.1 base score of 9.8 (CRITICAL).

This vulnerability has a CVSS 3.1 base score of 9.8, rated CRITICAL. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical Description

Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data. This affects Log4j versions up to 1.2 up to 1.2.17.

Remediation

Check the references section for vendor advisories and patches from apache. Update log4j to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected Products

Vendor Product Versions Status
apache log4j 0 Affected
netapp oncommand_system_manager 3.0 Affected
oracle communications_network_integrity 7.3.2 Affected
oracle financial_services_lending_and_leasing 14.1.0 Affected
oracle mysql_enterprise_monitor 0 Affected
oracle primavera_gateway 16.2 Affected
apache bookkeeper >= 0, < 4.14.3 Affected

Frequently Asked Questions

What is CVE-2019-17571?

CVE-2019-17571 is a critical-severity vulnerability affecting apache log4j. It was published on December 20, 2019 and has a CVSS 3.1 base score of 9.8 (CRITICAL).

How severe is CVE-2019-17571?

This vulnerability has a CVSS 3.1 base score of 9.8, rated CRITICAL. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2019-17571?

Check the references section for vendor advisories and patches from apache. Update log4j to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2019-17571?

CyberStrike's AI-powered security agents can automatically detect CVE-2019-17571 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.