# CVE-2017-5645: Deserialization of Untrusted Data in Log4j > Attackers can execute arbitrary code by sending crafted serialized payloads to Log4j's TCP or UDP socket servers. - **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:** 17 Apr 2017 - **Updated:** 8 Oct 2026 - **Also known as:** DEBIAN-CVE-2017-5645, GHSA-fxph-q3j8-mv87, RHSA-2017:1417, UBUNTU-CVE-2017-5645 ## What is CVE-2017-5645? CVE-2017-5645 is a critical unsafe deserialization vulnerability in Netapp Oncommand Insight, published on 17 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. Weakness: CWE-502 (Deserialization of Untrusted Data) ## Which versions are affected by CVE-2017-5645? 4 open source packages ship an affected version, including org.apache.logging.log4j:log4j and org.apache.logging.log4j:log4j-core. It affects 79 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.logging.log4j:log4j` | Maven | From 2.0 | 2.8.2 | | `org.apache.logging.log4j:log4j` | Maven | From 2.0 | 2.8.2 | | `org.apache.logging.log4j:log4j-core` | Maven | From 2.0 | 2.8.2 | | `org.apache.logging.log4j:log4j-core` | Maven | From 2.0 | 2.8.2 | | `rh-java-common-log4j` | Red Hat:rhel_software_collections:2::el6 | All versions | 0:1.2.17-15.15.el6 | | `rh-java-common-log4j-javadoc` | Red Hat:rhel_software_collections:2::el6 | All versions | 0:1.2.17-15.15.el6 | | `rh-java-common-log4j-manual` | Red Hat:rhel_software_collections:2::el6 | All versions | 0:1.2.17-15.15.el6 | | `rh-java-common-log4j` | Red Hat:rhel_software_collections:2::el7 | All versions | 0:1.2.17-15.15.el7 | | `rh-java-common-log4j-javadoc` | Red Hat:rhel_software_collections:2::el7 | All versions | 0:1.2.17-15.15.el7 | | `rh-java-common-log4j-manual` | Red Hat:rhel_software_collections:2::el7 | All versions | 0:1.2.17-15.15.el7 | Products: Apache Log4j, Netapp Oncommand Api Services, Netapp Oncommand Insight, Netapp Oncommand Workflow Automation, Netapp Service Level Manager, Netapp Snapcenter, Netapp Storage Automation Store, Oracle Api Gateway, Oracle Application Testing Suite, Oracle Autovue Vuelink Integration, Oracle Banking Platform, Oracle Bi Publisher, Oracle Communications Converged Application Server - Service Controller, Oracle Communications Instant Messaging Server, Oracle Communications Interactive Session Recorder, Oracle Communications Messaging Server, Oracle Communications Network Integrity, Oracle Communications Online Mediation Controller, Oracle Communications Pricing Design Center, Oracle Communications Service Broker and 59 more. ## How do I fix CVE-2017-5645? Upgrade org.apache.logging.log4j:log4j to 2.8.2 or later. ## Is CVE-2017-5645 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-5645 exists. Public exploit code: - CVE-2017-5645 - Apache Log4j RCE due Insecure Deserialization (github_poc): https://github.com/pimps/CVE-2017-5645 - 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 - Apache Log4j Server - Deserialization Command Execution (nuclei) ## Other vulnerabilities in Netapp Oncommand Insight - [CVE-2021-44228](https://insights.sbomify.com/CVE-2021-44228/): Apache Log4j2 Remote Code Execution (critical 10.0, exploited in the wild) - [CVE-2021-45046](https://insights.sbomify.com/CVE-2021-45046/): Apache Log4j2 Deserialization of Untrusted Data (critical 9.0, exploited in the wild) - [CVE-2022-23305](https://insights.sbomify.com/CVE-2022-23305/): SQL injection in JDBC Appender in Apache Log4j V1 (critical 9.8) - [CVE-2022-23302](https://insights.sbomify.com/CVE-2022-23302/): Deserialization of untrusted data in JMSSink in Apache Log4j 1.x (high 8.8) - [CVE-2023-26464](https://insights.sbomify.com/CVE-2023-26464/): Apache Log4j 1.x (EOL) allows DoS in Chainsaw and SocketAppender (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2017-5645 and fix it if it is affected. What it is: CVE-2017-5645 is a critical unsafe deserialization vulnerability in Netapp Oncommand Insight, published on 17 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-5645 exists. Affected packages and fixed versions: - org.apache.logging.log4j:log4j (Maven): affected from 2.0; fixed in 2.8.2 - org.apache.logging.log4j:log4j (Maven): affected from 2.0; fixed in 2.8.2 - org.apache.logging.log4j:log4j-core (Maven): affected from 2.0; fixed in 2.8.2 - org.apache.logging.log4j:log4j-core (Maven): affected from 2.0; fixed in 2.8.2 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-2017-5645/ (Markdown: https://insights.sbomify.com/CVE-2017-5645/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2017-5645 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-5645 - OSV: https://osv.dev/vulnerability/CVE-2017-5645 --- From sbomify Insights: https://insights.sbomify.com/CVE-2017-5645/ Summaries are generated and may contain mistakes; the official description above is the record.