CVE-2021-44228

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.

How to fix CVE-2021-44228

To remediate CVE-2021-44228, upgrade the affected package to a fixed version below.

• —upgrade to 2.15.0-1~deb11u1 or later
• —upgrade to 2.15.0-1~deb10u1 or later
• —upgrade to 2.7-2+deb9u1 or later
• —no fix listed
• —upgrade to 2.15.0 or later
• —upgrade to 1.9.2 or later
• —no fix listed
• —no fix listed

Is CVE-2021-44228 being exploited?

Yes — CVE-2021-44228 is on the CISA Known Exploited Vulnerabilities (KEV) catalog. Patch immediately.

Affected packages (8)

• from 0, < 2.15.0-1~deb11u1
• from 0, < 2.15.0-1~deb10u1
• from 0, < 2.7-2+deb9u1
• from 0, <= 1.2.1.2-jre17
• >= 2.13.0, < 2.15.0
• >= 1.8.0, < 1.9.2

CVSS scores

References (76)

• ADVISORYgithub.com/advisories/GHSA-7rjr-3q55-vv33
• ADVISORYnvd.nist.gov/vuln/detail/CVE-2021-44228
• ADVISORYsecurity-tracker.debian.org/tracker/CVE-2021-44228
• PATCHgithub.com/apache/logging-log4j2
• WEB