Risk Score
10.0
Out of 10
Summary
Identifier
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.
MergeBase Comment
We have released a public free tool for detecting vulnerable Log4J versions within any applications that are vulnerable. Available on GitHub here: https://github.com/mergebase/log4j-detector
We have also prepared a YouTube video that explains the vulnerability in detail, and shows how MergeBase can prevent attackers from exploiting this vulnerability in running unpatched production systems.
Common Weakness Enumeration (CWE)
