CVE-2021-44228
🟠 Medium In CISA KEVApache Log4j 2 (log4j-core). The exposure is transitive: the risk is rarely Log4j installed directly, but Log4j bundled inside something else, which is why inventories built from installed products missed it · 2.0-beta9 through 2.14.1, excluding the security releases 2.3.1, 2.12.2 and 2.12.3. Message lookup substitution was disabled by default in 2.15.0 and the JNDI lookup removed in 2.16.0
100.00th percentile
due 2021-12-24
Exploitation
Timeline
- 10/12/2021Added to the CISA KEV catalogue
- 10/12/2021CVE record published (CVE List)
- 24/12/2021CISA deadline for US federal agencies
- 16/11/2026BO Team used Log4Shell on vCenter to own a Russian software maker for months
Relationships
exploits suspected named in the same story vendor · Select a box to open its page · All relationships
Risk
Fix
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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
CWE-20,CWE-400,CWE-502