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

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). 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
    # 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
    # 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

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.