Apache Log4j2 vulnerable to RCE via JDBC Appender when attacker controls configuration
- 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.4, 2.3.2, 2.17.1, 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? →
- 2 proofs of concept on GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Apache Log4j2 versions 2.0-beta7 through 2.17.0 (excluding security fix releases 2.3.2 and 2.12.4) are vulnerable to a remote code execution (RCE) attack when a configuration uses a JDBC Appender with a JNDI LDAP data source URI when an attacker has control of the target LDAP server. This issue is fixed by limiting JNDI data source names to the java protocol in Log4j2 versions 2.17.1, 2.12.4, and 2.3.2.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- 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.4; From 2.4 · fixed in 2.3.2; From 2.0-beta7 · fixed in 2.17.1
- org.apache.logging.log4j:log4j-coreMaven
From 2.0-beta7 · fixed in 2.3.2
- org.apache.logging.log4j:log4j-coreMaven
From 2.4 · fixed in 2.12.4
- org.apache.logging.log4j:log4j-coreMaven
From 2.13.0 · fixed in 2.17.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.13
- org.ops4j.pax.logging:pax-logging-log4j2Maven
From 2.0.0 · fixed in 2.0.14