Skip to content

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

High severity GitHub Reviewed Published Mar 10, 2023 to the GitHub Advisory Database • Updated May 5, 2023

Package

maven org.apache.logging.log4j:log4j-core (Maven)

Affected versions

>= 1.0.4, < 2.0.0

Patched versions

2.0.0

Description

** UNSUPPORTED WHEN ASSIGNED ** When using the Chainsaw or SocketAppender components with Log4j 1.x on JRE less than 1.7, an attacker that manages to cause a logging entry involving a specially-crafted (ie deeply nested) hashmap or hashtable (depending on which logging component is in use) to be processed could exhaust the available memory in the virtual machine and achieve Denial of Service when the object is deserialized. This issue affects Apache Log4j before 2. Affected users are recommended to update to Log4j 2.x. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

References

Published by the National Vulnerability Database Mar 10, 2023
Published to the GitHub Advisory Database Mar 10, 2023
Reviewed Mar 10, 2023
Last updated May 5, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.206%
(59th percentile)

Weaknesses

CVE ID

CVE-2023-26464

GHSA ID

GHSA-vp98-w2p3-mv35

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.