Skip to content
fr Sign in
Not rated Exploited · ransomware Log4Shell

CVE-2021-44228 Apache Log4j2 Remote Code Execution Vulnerability

Active exploitation observed

· CISA KEV catalogue
Required action 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.
Ransomware campaigns Known to be used
Weakness CWE-20, CWE-502, CWE-400

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 products and versions

Product Affected versions Fixed in
Apache Log4j2 2.0 2.0-beta9 → latest No fix stated

References

Timeline

  1. Published
  2. Added to the KEV catalogue
  3. Last modified

Other CVEs of Apache Log4j2

The 3 CVEs of Apache Log4j2 →
CVE-2021-44832 Apache Log4j2 versions 2.0-beta7 through 2.17.0 (excluding security fix releases 2.3.2 and 2.12.4) are vulnerable to a… Not rated CVE-2021-45105 Apache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3 and 2.3.1) did not protect from uncontrolled… Not rated
Track this CVE