Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2019-17571: Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which ca

77
This week
CRITICAL 9.8REMOTEWATCHLISTUPGRADEMITIGATEMITIGATE

CVE-2019-17571 is a critical-severity flaw (CVSS 9.8) affecting log4j, debian linux, ubuntu linux. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • Critical severity
  • EPSS top 1%: very likely to be exploited
  • Public exploit reference
  • CISA SSVC: automatable with total technical impact
  • Remotely exploitable, no login, no user action
  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score9.8 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance70.0% (top 1%)
CISA exploited listNo
WeaknessCWE-502
Published2019-12-20
Last modified2026-06-17
Publisher (CNA): Apache Software Foundation · Vendor: apache · canonical · debian · netapp · opensuse

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

apache log4j UPGRADE
Affected: <= 1.2.17
Fixed in: newer than 1.2.17
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy log4j || rpm -q log4j || log4j --version
2. UPGRADE to newer than 1.2.17 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade log4j
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade log4j
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
debian debian linux MITIGATE
Affected: 8.0 · 9.0 · 10.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 8.0
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
canonical ubuntu linux MITIGATE
Affected: 18.04
Fixed in: no fixed release known
Safe to downgrade to: a release before 18.04
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
opensuse leap MITIGATE
Affected: 15.1
Fixed in: no fixed release known
Safe to downgrade to: a release before 15.1
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
netapp oncommand system manager UPGRADE
Affected: >= 3.0 and <= 3.1.3
Fixed in: newer than 3.1.3
Safe to downgrade to: a release before 3.0
1. Check installed version
apt-cache policy oncommand-system-manager || rpm -q oncommand-system-manager || oncommand-system-manager --version
2. UPGRADE to newer than 3.1.3 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade oncommand-system-manager
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade oncommand-system-manager
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 3.0 (Debian / Ubuntu)
apt-cache madison oncommand-system-manager sudo apt install oncommand-system-manager=<VERSION_BEFORE_3.0> sudo apt-mark hold oncommand-system-manager
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list oncommand-system-manager sudo dnf downgrade oncommand-system-manager-<VERSION_BEFORE_3.0> sudo dnf versionlock add oncommand-system-manager
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
netapp oncommand workflow automation MITIGATE
Affected: all versions
Fixed in: no fixed release known
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy oncommand-workflow-automation || rpm -q oncommand-workflow-automation || oncommand-workflow-automation --version
No fixed or unaffected release known
Apply the vendor mitigation from the advisory, disable the affected feature, or restrict network access.

Exact fixes by distribution

A distro patch exists: prefer upgrading over downgrading.
Maven · log4j:log4j · NO FIX YET · vulnerable: >= 1.2, <= 1.2.17 · source
Maven · org.zenframework.z8.dependencies.commons:log4j-1.2.17 · NO FIX YET · vulnerable: = 2.0 · source
Fedora 46 · libopenmpt · FIXED · 0.8.10-2.fc46 · FEDORA-2026-a9998621be · source
sudo dnf upgrade --advisory=FEDORA-2026-a9998621be
Debian 12 · apache-log4j1.2 · FIXED · 1.2.17-9
sudo apt update && sudo apt install --only-upgrade apache-log4j1.2 dpkg --compare-versions "$(dpkg-query -W -f='${Version}' apache-log4j1.2)" ge "1.2.17-9" && echo PATCHED || echo STILL-VULNERABLE
Debian 13 · apache-log4j1.2 · FIXED · 1.2.17-9
sudo apt update && sudo apt install --only-upgrade apache-log4j1.2 dpkg --compare-versions "$(dpkg-query -W -f='${Version}' apache-log4j1.2)" ge "1.2.17-9" && echo PATCHED || echo STILL-VULNERABLE
RHEL 6 Extended Lifecycle Support · log4j · FIXED · log4j-1.2.14-6.7.el6_10
sudo dnf upgrade --advisory=RHSA-2022:5053 rpm -q log4j
RHEL 7 · log4j · FIXED · log4j-1.2.17-16.el7_4
sudo dnf upgrade --advisory=RHSA-2017:2423 rpm -q log4j
RHEL 5 · log4j · DEFERRED
RHEL 8 · parfait:0.5/log4j12 · NOT AFFECTED
Amazon Linux 2 · see advisory · FIXED · ALAS2-2022-1739 · source
sudo yum update --advisory=ALAS2-2022-1739
Amazon Linux 1 · see advisory · FIXED · ALAS-2022-1562 · source
sudo yum update --advisory=ALAS-2022-1562

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-17571?

log4j: upgrade to newer than 1.2.17; debian linux: mitigate or apply the listed mitigation; ubuntu linux: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2019-17571 being exploited?

CVE-2019-17571 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-17571 affect?

CVE-2019-17571 affects log4j, debian linux, ubuntu linux. Severity is critical (CVSS 9.8). 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

How urgent is CVE-2019-17571?

Priority 77/100. Critical severity; EPSS top 1%: very likely to be exploited; Public exploit reference; CISA SSVC: automatable with total technical impact; Remotely exploitable, no login, no user action; On your watchlist

Software pages

Apache Log4j vulnerabilities · Ubuntu vulnerabilities · Debian vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.