Log4Shell: Apache Log4j2 JNDI features do not protect against attacker controlled LDAP and other JNDI related endpoints
Affects Apache Log4j2 versions earlier than 2.15.0 when message lookup substitution is enabled. Fixed in Log4j2 2.15.0, and Debian bullseye has 2.15.0-1~deb11u1.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- Yes, on CISA KEV
- Fix
- Fixed in 2.3.1, 2.12.2, 2.15.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2.3.1, 2.12.2, 2.15.0.
- Last modified
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 100.0% · 100th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 92/100
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Actively exploited
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 3 on Exploit-DB, 5 Metasploit modules, 505 proofs of concept on GitHub, 1 Nuclei template
- Exploitation: active
- Automatable: yes
- Technical impact: total
Summary
Apache Log4j2, a widely used Java logging library, is affected, and an attacker who can control logged messages or their parameters may be able to run arbitrary code loaded from malicious LDAP or other JNDI servers. This could allow full compromise of the system running the affected software.
Read the original description
Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12.3, and 2.3.1) JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled. From log4j 2.15.0, this behavior has been disabled by default. From version 2.16.0 (along with 2.12.2, 2.12.3, and 2.3.1), this functionality has been completely removed. Note that this vulnerability is specific to log4j-core and does not affect log4net, log4cxx, or other Apache Logging Services projects.
cve.now Index
- Exploitation40/40Listed in CISA's Known Exploited Vulnerabilities catalog
- Exposure25/25Actively exploited, CISA rates it automatable
- Reach17/20Affects Log4j (a widely deployed server, runtime, framework or database)
- Severity10/10CVSS 10.0, total technical impact per CISA
- No patch0/5No signal
Impact
- Widely used
“In fact, data from Sonatype as of February 16, 2022 indicates 39% of Log4j downloads are still versions vulnerable to Log4Shell.”Source: rapid7.com
3.6k stars on GitHub.Source: apache/logging-log4j2
241 packages depend on org.apache.logging.log4j:log4j-core.Source: deps.dev
What to do
Upgrade to a fixed version: 2.3.1, 2.12.2, 2.15.0.
Fix it by , CISA's deadline for US federal agencies.
Timeline
- CVE published
- Added to CISA KEV
CISA has evidence of exploitation in the wild
4 days - Public exploit on Exploit-DB
EDB-50592, EDB-50590, EDB-51183
10 days - CISA remediation deadline
Due date for US federal agencies to patch
1,138 days (about 3 years) - CISA SSVC assessment
Exploitation: active · Automatable: yes · Technical impact: total
259 days - Record last updated377 days (about 1 year)
- Exploit code on GitHub
ShyVictor/minecraft-rce-lab
Affected versions
- Apache Software Foundation Apache Log4j2
From 2.0-beta9 · fixed in 2.3.1; From 2.4 · fixed in 2.12.2; From 2.13.0 · fixed in 2.15.0
From 2.13.0 · fixed in 2.15.0
Fixed in 2.15.0 (released Dec 9, 2021, 1 day before disclosure).
From 2.0-beta9 · fixed in 2.3.1
Fixed in 2.3.1 (released Dec 21, 2021, 11 days after disclosure).
From 2.4 · fixed in 2.12.2
Fixed in 2.12.2 (released Dec 14, 2021, 4 days after disclosure).
The latest release, 2.26.1, is not affected.
through 1.2.1.2-jre17
Fixed in 1.2.2.1 (released Feb 9, 2022, 61 days after disclosure), the first release outside every affected range (no listed fixed version clears them all).
The latest release, 1.2.2.1-jre17, is not affected.
6.3.2.1
No fix released. The latest release, 6.3.2.1, is still affected.
2.6.3-CUSTOM
No fix released. The latest release, 2.6.3-CUSTOM, is still affected.
From 1.8.0 · fixed in 1.9.2
Fixed in 1.9.2 (released Jan 31, 2022, 52 days after disclosure).
Show all 11 packagesShow fewer packages
From 1.10.0 · fixed in 1.10.8
Fixed in 1.10.8 (released Dec 19, 2021, 9 days after disclosure).
From 1.11.0 · fixed in 1.11.10
Fixed in 1.11.10 (released Dec 10, 2021, the day of disclosure).
From 2.0.0 · fixed in 2.0.11
Fixed in 2.0.11 (released Dec 10, 2021, the day of disclosure).
The latest release, 2.3.5, is not affected.
On X 6
Evidence 537
- Advisory
- Advisory
- Advisory
- Advisory
- Exploit
Show all 537 sourcesShow fewer sources
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Exploit
- Link
- Link
- Link
- Link
- Link
- Link
- Link
- Link
- Link
- Link
- Link
- Link
- Link
- Link
- Link
- Link
- Link
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2021-44228
Is CVE-2021-44228 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2021-12-10, which means it has evidence of attacks. US federal agencies must fix it by 2021-12-24. Public exploit code exists (Exploit-DB, Metasploit, a proof of concept on GitHub). Its EPSS score, the predicted chance of exploitation in the next 30 days, reached 10% or higher by 2026-10-22.Source: cisa.gov, cve.now feed data
What does this mean?
Log4j2's JNDI features do not restrict what endpoints they contact. An attacker who can control log messages or log message parameters can make it execute arbitrary code loaded from LDAP servers, when message lookup substitution is enabled.Source: sec.cloudapps.cisco.com, lists.debian.org
Which versions are affected by CVE-2021-44228?
Apache Log4j2: from 2.0-beta9 before 2.3.1; from 2.4 before 2.12.2; from 2.13.0 before 2.15.0. org.apache.logging.log4j:log4j-core (Maven): from 2.13.0 before 2.15.0. org.apache.logging.log4j:log4j-core (Maven): from 2.0-beta9 before 2.3.1. org.apache.logging.log4j:log4j-core (Maven): from 2.4 before 2.12.2. com.guicedee.services:log4j-core (Maven): through 1.2.1.2-jre17. 6 more packages are listed on the page.Source: cve.now feed data
Am I affected, and how do I check?
Apache Log4j2 versions 2.0-beta9 through 2.3.1, 2.4 through 2.12.2, and 2.13.0 through 2.15.0 are listed as affected, along with the log4j-core and pax-logging-log4j2 packages in the affected list. Check the log4j-core or pax-logging version in your dependency files or jar names, and whether message lookup substitution is enabled.Source: sec.cloudapps.cisco.com, lists.debian.org
How do I fix CVE-2021-44228?
Upgrade Apache Log4j2 to 2.15.0 or later. For pax-logging-log4j2, use 1.9.2, 1.10.8, 1.11.10, or 2.0.11 depending on your release line. Debian bullseye has the fix in 2.15.0-1~deb11u1.Source: sec.cloudapps.cisco.com, lists.debian.org