# CVE-2019-17571: Deserialization of Untrusted Data in Log4j > Remote attackers can execute arbitrary code via deserialization in Log4j 1.x SocketServer if configured to listen for untrusted network traffic. - **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 20 Dec 2019 - **Updated:** 28 May 2026 - **Also known as:** CLEANSTART-2026-EJ90650, CLSA-2022-1655842760, CLSA-2022-1655843011, DEBIAN-CVE-2019-17571, DLA-2065-1, DSA-4686-1, GHSA-2qrg-x229-3v8q, MINI-558h-v443-423m, MINI-h7gg-w5m8-g53m, RHSA-2022:5053, ROOT-APP-MAVEN-CVE-2019-17571, SUSE-SU-2020:0053-1, SUSE-SU-2020:0054-1, SUSE-SU-2020:14267-1, UBUNTU-CVE-2019-17571, USN-4495-1, openSUSE-SU-2020:0051-1 ## What is CVE-2019-17571? CVE-2019-17571 is a critical unsafe deserialization vulnerability in Canonical Ubuntu Linux, published on 20 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. Weakness: CWE-502 (Deserialization of Untrusted Data) ## Which versions are affected by CVE-2019-17571? 4 open source packages ship an affected version, including log4j:log4j and org.zenframework.z8.dependencies.commons:log4j-1.2.17. It affects 17 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `log4j:log4j` | Maven | From 1.2 to 1.2.17 | None | | `log4j:log4j` | Maven | From 1.2 to 1.2.17 | None | | `org.zenframework.z8.dependencies.commons:log4j-1.2.17` | Maven | All versions | None | | `org.zenframework.z8.dependencies.commons:log4j-1.2.17` | Maven | All versions | None | | `log4j` | Red Hat:rhel_els:6 | All versions | 0:1.2.14-6.7.el6_10 | | `log4j-debuginfo` | Red Hat:rhel_els:6 | All versions | 0:1.2.14-6.7.el6_10 | | `log4j-javadoc` | Red Hat:rhel_els:6 | All versions | 0:1.2.14-6.7.el6_10 | | `log4j-manual` | Red Hat:rhel_els:6 | All versions | 0:1.2.14-6.7.el6_10 | | `log4j` | SUSE:Enterprise Storage 5 | All versions | 1.2.15-126.3.1 | | `log4j` | SUSE:HPE Helion OpenStack 8 | All versions | 1.2.15-126.3.1 | | `log4j` | SUSE:Linux Enterprise Module for Basesystem 15 | All versions | 1.2.17-5.3.1 | | `log4j` | SUSE:Linux Enterprise Module for Basesystem 15 SP1 | All versions | 1.2.17-5.3.1 | | `log4j` | SUSE:Linux Enterprise Module for Development Tools 15 | All versions | 1.2.17-5.3.1 | | `log4j` | SUSE:Linux Enterprise Module for Development Tools 15 SP1 | All versions | 1.2.17-5.3.1 | | `log4j` | SUSE:Linux Enterprise Point of Sale 11 SP3 | All versions | 1.2.15-26.32.14.1 | | `log4j` | SUSE:Linux Enterprise Server 11 SP4-LTSS | All versions | 1.2.15-26.32.14.1 | | `log4j` | SUSE:Linux Enterprise Server 12 SP1-LTSS | All versions | 1.2.15-126.3.1 | | `log4j` | SUSE:Linux Enterprise Server 12 SP2-BCL | All versions | 1.2.15-126.3.1 | | `log4j` | SUSE:Linux Enterprise Server 12 SP2-LTSS | All versions | 1.2.15-126.3.1 | | `log4j` | SUSE:Linux Enterprise Server 12 SP3-BCL | All versions | 1.2.15-126.3.1 | | `log4j` | SUSE:Linux Enterprise Server 12 SP3-LTSS | All versions | 1.2.15-126.3.1 | | `log4j` | SUSE:Linux Enterprise Server 12 SP4 | All versions | 1.2.15-126.3.1 | | `log4j` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 1.2.15-126.3.1 | | `log4j` | SUSE:Linux Enterprise Server for SAP Applications 12 SP1 | All versions | 1.2.15-126.3.1 | | `log4j` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 1.2.15-126.3.1 | | `log4j` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 1.2.15-126.3.1 | | `log4j` | SUSE:Linux Enterprise Server for SAP Applications 12 SP4 | All versions | 1.2.15-126.3.1 | | `log4j` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 1.2.15-126.3.1 | | `log4j` | SUSE:Linux Enterprise Software Development Kit 12 SP4 | All versions | 1.2.15-126.3.1 | | `log4j` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 1.2.15-126.3.1 | | `log4j` | SUSE:OpenStack Cloud 7 | All versions | 1.2.15-126.3.1 | | `log4j` | SUSE:OpenStack Cloud 8 | All versions | 1.2.15-126.3.1 | | `log4j` | SUSE:OpenStack Cloud Crowbar 8 | All versions | 1.2.15-126.3.1 | | `log4j` | openSUSE:Leap 15.1 | All versions | 1.2.17-lp151.5.3.1 | | `log4j-mini` | openSUSE:Leap 15.1 | All versions | 1.2.17-lp151.5.3.1 | Products: Apache Bookkeeper, Apache Log4j, Canonical Ubuntu Linux, Debian Debian Linux, Netapp Oncommand System Manager, Netapp Oncommand Workflow Automation, Opensuse Leap, Oracle Application Testing Suite, Oracle Communications Network Integrity, Oracle Endeca Information Discovery Studio, Oracle Financial Services Lending and Leasing, Oracle Mysql Enterprise Monitor, Oracle Primavera Gateway, Oracle Rapid Planning, Oracle Retail Extract Transform and Load, Oracle Retail Service Backbone, Oracle Weblogic Server. ## How do I fix CVE-2019-17571? Product is end of life, replace it. ## Is CVE-2019-17571 being exploited? There is no known exploitation of CVE-2019-17571 in the wild and no public exploit code. Public exploit code: - Apache Log4j 1.2.X存在反序列化远程代码执行漏洞 (github_poc): https://github.com/shadow-horse/CVE-2019-17571 - Fastest filesystem scanner for log4shell (CVE-2021-44228, CVE-2021-45046) and other vulnerable (CVE-2017-5645, CVE-2019-17571, CVE-2022-23305, CVE-2022-23307 ... ) instances of log4j library. Excellent performance and low memory footprint. (github_poc): https://github.com/HynekPetrak/log4shell-finder - Environment for CVE_2019_17571 (github_poc): https://github.com/Al1ex/CVE-2019-17571 ## Other vulnerabilities in Canonical Ubuntu Linux - [CVE-2017-6891](https://insights.sbomify.com/CVE-2017-6891/): Memory corruption in GnuTLS libtasn1 (high 8.8) - [CVE-2020-36230](https://insights.sbomify.com/CVE-2020-36230/): A flaw was discovered in OpenLDAP before 2.4.57 leading in an assertion failure in slapd in the X.509 DN parsing in decode.c ber_next_elemen (high 7.5) - [CVE-2019-19906](https://insights.sbomify.com/CVE-2019-19906/): Memory corruption in n/a (high 7.5) - [CVE-2020-23922](https://insights.sbomify.com/CVE-2020-23922/): Memory corruption in n/a (high 7.1) - [CVE-2022-32531](https://insights.sbomify.com/CVE-2022-32531/): Apache BookKeeper: Java Client Uses Connection to Host that Failed Hostname Verification (medium 5.9) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-17571 and fix it if it is affected. What it is: CVE-2019-17571 is a critical unsafe deserialization vulnerability in Canonical Ubuntu Linux, published on 20 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2019-17571 in the wild and no public exploit code. Affected packages and fixed versions: - log4j:log4j (Maven): affected from 1.2 up to 1.2.17; no fix listed - log4j:log4j (Maven): affected from 1.2 up to 1.2.17; no fix listed - org.zenframework.z8.dependencies.commons:log4j-1.2.17 (Maven): affected all versions; no fix listed - org.zenframework.z8.dependencies.commons:log4j-1.2.17 (Maven): affected all versions; no fix listed Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2019-17571/ (Markdown: https://insights.sbomify.com/CVE-2019-17571/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-17571 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-17571 - OSV: https://osv.dev/vulnerability/CVE-2019-17571 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-17571/ Summaries are generated and may contain mistakes; the official description above is the record.