Log4j versions prior to 2.16.0 are subject to a remote code execution vulnerability via the ldap JNDI parser.
As per Apache's Log4j security guide: Apache Log4j2 <=2.14.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.16.0, this behavior has been disabled by default.
Log4j version 2.15.0 contained an earlier fix for the vulnerability, but that patch did not disable attacker-controlled JNDI lookups in all situations. For more information, see the Updated advice for version 2.16.0 section of this advisory.
Logging untrusted or user controlled data with a vulnerable version of Log4J may result in Remote Code Execution (RCE) against your application. This includes untrusted data included in logged errors such as exception traces, authentication failures, and other unexpected vectors of user controlled input.
Any Log4J version prior to v2.15.0 is affected to this specific issue.
The v1 branch of Log4J which is considered End Of Life (EOL) is vulnerable to other RCE vectors so the recommendation is to still update to 2.16.0 where possible.
Additional backports of this fix have been made available in versions 2.3.1, 2.12.2, and 2.12.3
Only the org.apache.logging.log4j:log4j-core package is directly affected by this vulnerability. The org.apache.logging.log4j:log4j-api should be kept at the same version as the org.apache.logging.log4j:log4j-core package to ensure compatability if in use.
The Apache Logging Services team provided updated mitigation advice upon the release of version 2.16.0, which disables JNDI by default and completely removes support for message lookups.
Even in version 2.15.0, lookups used in layouts to provide specific pieces of context information will still recursively resolve, possibly triggering JNDI lookups. This problem is being tracked as CVE-2021-45046. More information is available on the GitHub Security Advisory for CVE-2021-45046.
Users who want to avoid attacker-controlled JNDI lookups but cannot upgrade to 2.16.0 must ensure that no such lookups resolve to attacker-provided data and ensure that the the JndiLookup class is not loaded.
Please note that Log4J v1 is End Of Life (EOL) and will not receive patches for this issue. Log4J v1 is also vulnerable to other RCE vectors and we recommend you migrate to Log4J 2.16.0 where possible.
| Score | Percentile |
|---|---|
| 94.36% | 99.96% |
| Base score | Version | Severity | Vector |
|---|---|---|---|
| 10.0 | 3.1 | — |
|
| Type | Value |
|---|---|
| GHSA | GHSA-jfh8-c2jp-5v3q ↗ |
| CVE | CVE-2021-44228 ↗ |
Vulnerable version ranges and first patched releases as published by GitHub.
| Ecosystem | Package | Vulnerable range | First patched | Vulnerable functions |
|---|---|---|---|---|
| maven | org.apache.logging.log4j:log4j-core | >= 2.13.0, < 2.15.0 | 2.15.0 | — |
| maven | org.apache.logging.log4j:log4j-core | >= 2.4, < 2.12.2 | 2.12.2 | — |
| maven | com.guicedee.services:log4j-core | <= 1.2.1.2-jre17 | — | — |
| maven | org.xbib.elasticsearch:log4j | = 6.3.2.1 | — | — |
| maven | uk.co.nichesolutions.logging.log4j:log4j-core | = 2.6.3-CUSTOM | — | — |
| maven | org.apache.logging.log4j:log4j-core | >= 2.0-beta9, < 2.3.1 | 2.3.1 | — |
| maven | org.ops4j.pax.logging:pax-logging-log4j2 | >= 1.8.0, < 1.9.2 | 1.9.2 | — |
| maven | org.ops4j.pax.logging:pax-logging-log4j2 | >= 1.10.0, < 1.10.8 | 1.10.8 | — |
| maven | org.ops4j.pax.logging:pax-logging-log4j2 | >= 1.11.0, < 1.11.10 | 1.11.10 | — |
| maven | org.ops4j.pax.logging:pax-logging-log4j2 | >= 2.0.0, < 2.0.11 | 2.0.11 | — |