CVE-2023-26464: Apache Log4j 1.x (EOL) allows Denial of Service (DoS)

CVE-2023-26464 · Severity: low · CVSS 3.1 · Published 2023-03-10

Apache Log4j 1.x (EOL) allows Denial of Service (DoS)

Technologies: log4j:log4j (Maven), org.apache.logging.log4j:log4j-core (Maven). Vendors: Maven.

Quick answers

Is CVE-2023-26464 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2023-26464 being exploited in the wild.
How severe is CVE-2023-26464?
Low severity, with a CVSS score of 3.1, published 10 March 2023.
Which products and versions are affected?
log4j:log4j (Maven) ECOSYSTEM:introduced=1.0.4,fixed=2.0; org.apache.logging.log4j:log4j-core (Maven) ECOSYSTEM:introduced=1.0.4,fixed=2.0.
Is there a fix for CVE-2023-26464?
Yes. log4j:log4j (Maven): upgrade to 2.0 or later; org.apache.logging.log4j:log4j-core (Maven): upgrade to 2.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2023-26464?
Check whether you run 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

  • log4j:log4j (Maven): upgrade to 2.0 or later
    # set log4j:log4j to 2.0 in your pom.xml or build.gradle
  • org.apache.logging.log4j:log4j-core (Maven): upgrade to 2.0 or later
    # set org.apache.logging.log4j:log4j-core to 2.0 in your pom.xml or build.gradle

Affected products

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

Identifiers

  • CVE-2023-26464
  • GHSA-vp98-w2p3-mv35

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