# CVE-2017-5645: Deserialization of Untrusted Data in Log4j

Source: https://junglewise.ai/threats/cve-2017-5645-deserialization-of-untrusted-data-in-log4j  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2020-01-06  
License: CC BY 4.0 with a link back

CVE-2017-5645 · Severity: low · CVSS 3 · Published 2020-01-06

Deserialization of Untrusted Data in Log4j

Technologies: [org.apache.logging.log4j:log4j-core (Maven)](https://junglewise.ai/threats/technologies/org-apache-logging-log4j-log4j-core). Vendors: [Maven](https://junglewise.ai/threats/vendors/maven).

## Quick answers

**Is CVE-2017-5645 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2017-5645 being exploited in the wild.

**How severe is CVE-2017-5645?** Low severity, with a CVSS score of 3, published 6 January 2020.

**Which products and versions are affected?** org.apache.logging.log4j:log4j (Maven) ECOSYSTEM:introduced=2.0,fixed=2.8.2; org.apache.logging.log4j:log4j-core (Maven) ECOSYSTEM:introduced=2.0,fixed=2.8.2.

**Is there a fix for CVE-2017-5645?** Yes. org.apache.logging.log4j:log4j (Maven): upgrade to 2.8.2 or later; org.apache.logging.log4j:log4j-core (Maven): upgrade to 2.8.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2017-5645?** Check whether you run org.apache.logging.log4j:log4j (Maven) or org.apache.logging.log4j:log4j-core (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.

## How to fix

- org.apache.logging.log4j:log4j (Maven): upgrade to 2.8.2 or later

  ```sh
  # set org.apache.logging.log4j:log4j to 2.8.2 in your pom.xml or build.gradle
  ```

- org.apache.logging.log4j:log4j-core (Maven): upgrade to 2.8.2 or later

  ```sh
  # set org.apache.logging.log4j:log4j-core to 2.8.2 in your pom.xml or build.gradle
  ```


## Affected products

- org.apache.logging.log4j:log4j (Maven) ECOSYSTEM:introduced=2.0,fixed=2.8.2
- org.apache.logging.log4j:log4j-core (Maven) ECOSYSTEM:introduced=2.0,fixed=2.8.2

## Identifiers

- CVE-2017-5645
- GHSA-fxph-q3j8-mv87

## Related threats

- [Apache Log4j Core invalid XML output in XmlLayout](https://junglewise.ai/threats/cve-2026-34480-apache-log4j-core-invalid-xml-output-in-xmllayout)
- [Apache Log4j Core log injection in Rfc5424Layout](https://junglewise.ai/threats/cve-2026-34478-apache-log4j-core-log-injection-in-rfc5424layout)
- [Apache Log4j Core improper certificate validation in network appenders](https://junglewise.ai/threats/cve-2026-34477-apache-log4j-core-improper-certificate-validation-in-network)
- [Apache Log4j does not verify the TLS hostname in its Socket Appender](https://junglewise.ai/threats/cve-2025-68161-apache-log4j-does-not-verify-the-tls-hostname-in-its-socket)
- [Apache Log4j 1.x (EOL) allows Denial of Service (DoS)](https://junglewise.ai/threats/cve-2023-26464-apache-log4j-1-x-eol-allows-denial-of-service-dos)