cve.bz

CVE-2021-45046

9.0 criticalKEVEPSS 100%

Critical (9.0) in Apache Log4j2. In CISA KEV since 2023-05-01, with known ransomware use. EPSS 100% chance of exploitation in the next 30 days. Fixed in org.apache.logging.log4j:log4j-core 2.12.2, 2.16.0, 2.3.1.

It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allows attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in an information leak and remote code execution in some environments and local code execution in all environments. Log4j 2.16.0 (Java 8) and 2.12.2 (Java 7) fix this issue by removing support for message lookup patterns and disabling JNDI functionality by default.

Severity

CVSS 3.1

9.0 critical
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
EPSS
100% chance of exploitation in the next 30 days; higher than 99% of CVEs (scores of 2026-10-31)
CISA KEV
listed 2023-05-01, due 2023-05-22, known ransomware use
CWE
CWE-917
Published
Modified
Record from
the NVD, synced

Affected

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-7rjr-3q55-vv33Mavenorg.apache.logging.log4j:log4j-core>=2.13.0 <2.16.02.16.0
GHSA-7rjr-3q55-vv33Mavenorg.apache.logging.log4j:log4j-core>=2.4.0 <2.12.22.12.2
GHSA-7rjr-3q55-vv33Mavenorg.ops4j.pax.logging:pax-logging-log4j2>=1.8.0 <1.9.21.9.2
GHSA-7rjr-3q55-vv33Mavenorg.ops4j.pax.logging:pax-logging-log4j2>=1.10.0 <1.10.81.10.8
GHSA-7rjr-3q55-vv33Mavenorg.ops4j.pax.logging:pax-logging-log4j2>=1.11.0 <1.11.111.11.11
GHSA-7rjr-3q55-vv33Mavenorg.ops4j.pax.logging:pax-logging-log4j2>=2.0.0 <2.0.122.0.12
GHSA-7rjr-3q55-vv33Mavenorg.apache.logging.log4j:log4j-core<2.3.12.3.1

References

Check your stackJSON