Log in Start free

Actively exploited · Published Dec 10, 2021 · Assigned by apache

CVE-2021-44228Apache Log4j2 JNDI features do not protect against attacker controlled LDAP and other JNDI related endpoints

Critical 10.0 Exploited Ransomware

In plain English

A critical-severity unsafe deserialization in Apache Log4j2 from Apache Software Foundation. Attackers are actively exploiting it in the wild (listed by CISA on December 10, 2021). It has been used in ransomware campaigns. The chance it is exploited in the next 30 days is estimated at 100.0% (higher than 99.9% of all known vulnerabilities). Ready-made attack tooling exists: Metasploit, Nuclei, public proof-of-concept code. Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)10.0Critical
Exploit odds (30 days)100.0%top 0.0% of all CVEs
Exploited in the wildYesCISA KEV since Dec 10, 2021
Attack tooling3Metasploit, Nuclei, Public PoC

CISA guidance

For all affected software assets for which updates exist, the only acceptable remediation actions are: 1) Apply updates; OR 2) remove affected assets from agency networks. Temporary mitigations using one of the measures provided at https://www.cisa.gov/uscert/ed-22-02-apache-log4j-recommended-mitigation-measures are only acceptable until updates are available.

Federal agencies must remediate by Dec 24, 2021.

Official 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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12apache-log4j22.15.0-1DEBIAN-CVE-2021-44228
Debian:13apache-log4j22.15.0-1DEBIAN-CVE-2021-44228
Debian:14apache-log4j22.15.0-1DEBIAN-CVE-2021-44228
Mavencom.guicedee.services:log4j-coreno fix listedGHSA-jfh8-c2jp-5v3q
Mavenorg.apache.logging.log4j:log4j-core2.15.0GHSA-jfh8-c2jp-5v3q
Mavenorg.apache.logging.log4j:log4j-core2.3.1GHSA-jfh8-c2jp-5v3q
Mavenorg.apache.logging.log4j:log4j-core2.12.2GHSA-jfh8-c2jp-5v3q
Mavenorg.ops4j.pax.logging:pax-logging-log4j21.10.8GHSA-jfh8-c2jp-5v3q
Mavenorg.ops4j.pax.logging:pax-logging-log4j21.11.10GHSA-jfh8-c2jp-5v3q
Mavenorg.ops4j.pax.logging:pax-logging-log4j22.0.11GHSA-jfh8-c2jp-5v3q
Mavenorg.ops4j.pax.logging:pax-logging-log4j21.9.2GHSA-jfh8-c2jp-5v3q
Mavenorg.xbib.elasticsearch:log4jno fix listedGHSA-jfh8-c2jp-5v3q
Mavenuk.co.nichesolutions.logging.log4j:log4j-coreno fix listedGHSA-jfh8-c2jp-5v3q

Affected products (as reported)

VendorProductVersions
Apache Software Foundation Apache Log4j2 2.0-beta9 – before log4j-core*

Weakness: CWE-502, CWE-400, CWE-20 · Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

References