Apache Log4j2 does not always protect from infinite recursion in lookup evaluation
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.12.3, 2.3.1, 2.17.0, 1.9.2, 1.10.9, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 7 proofs of concept on GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Apache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3 and 2.3.1) did not protect from uncontrolled recursion from self-referential lookups. This allows an attacker with control over Thread Context Map data to cause a denial of service when a crafted string is interpreted. This issue was fixed in Log4j 2.17.0, 2.12.3, and 2.3.1.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
- EPSS reached 10%
FIRST estimates at least a 10% chance of exploitation in the next 30 days
Affected versions
- Apache Software Foundation Apache Log4j2
From log4j-core · fixed in 2.12.3; From 2.4 · fixed in 2.3.1; From 2.0-alpha1 · fixed in 2.17.0
- org.apache.logging.log4j:log4j-coreMaven
From 2.4.0 · fixed in 2.12.3
- org.apache.logging.log4j:log4j-coreMaven
From 2.13.0 · fixed in 2.17.0
- org.apache.logging.log4j:log4j-coreMaven
fixed in 2.3.1
- org.ops4j.pax.logging:pax-logging-log4j2Maven
From 1.8.0 · fixed in 1.9.2
- org.ops4j.pax.logging:pax-logging-log4j2Maven
From 1.10.0 · fixed in 1.10.9
- org.ops4j.pax.logging:pax-logging-log4j2Maven
From 1.11.0 · fixed in 1.11.12
- org.ops4j.pax.logging:pax-logging-log4j2Maven
From 2.0.0 · fixed in 2.0.13