BlogPHP2Shell Exploitation: How Secure.com Can Protect YouRead more
← CVE Radar

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

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.

10.0 CRITICALEPSS 99.99%⚡ Known Exploited (CISA KEV)NVD: Analyzed

Overview

Severity

ScoreSeverityVersionVector String
10.0CRITICAL3.1NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
9.3HIGH2.0NVDAV:N/AC:M/Au:N/C:C/I:C/A:C

CISA required action

⚡ Known exploited · remediation due Dec 24, 2021

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.

Details

CVE ID
CVE-2021-44228
Status
Analyzed
Assigner (CNA)
apache
Published
Dec 10, 2021
Last modified
2026-08-11 19:33 UTC
Weaknesses

Sources

Refreshed hourly from the sources above. Last fetched 2026-11-08 11:24 UTC.