Apache Log4j2 versions 2.0-beta7 through 2.17.0 (excluding security fix releases 2.3.2 and 2.12.4) are vulnerable to an attack where an attacker with permission to modify the logging configuration file can construct a malicious configuration using a JDBC Appender with a data source referencing a JNDI URI which can execute remote code. This issue is fixed by limiting JNDI data source names to the java protocol in Log4j2 versions 2.17.1, 2.12.4, and 2.3.2. # Affected packages 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. This issue does not impact default configurations of Log4j2 and requires an attacker to have control over the Log4j2 configuration, which reduces the likelihood of being exploited.
Update org.apache.logging.log4j:log4j-core to 2.3.2; org.apache.logging.log4j:log4j-core to 2.12.4; org.apache.logging.log4j:log4j-core to 2.17.1; org.ops4j.pax.logging:pax-logging-log4j2 to 1.9.2; org.ops4j.pax.logging:pax-logging-log4j2 to 1.10.9; org.ops4j.pax.logging:pax-logging-log4j2 to 1.11.13; org.ops4j.pax.logging:pax-logging-log4j2 to 2.0.14 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanImproper Input Validation and Injection in Apache Log4j2 affects org.apache.logging.log4j:log4j-core (maven), org.apache.logging.log4j:log4j-core (maven), org.apache.logging.log4j:log4j-core (maven), org.ops4j.pax.logging:pax-logging-log4j2 (maven), org.ops4j.pax.logging:pax-logging-log4j2 (maven), org.ops4j.pax.logging:pax-logging-log4j2 (maven), org.ops4j.pax.logging:pax-logging-log4j2 (maven). Severity is medium. Apache Log4j2 versions 2.0-beta7 through 2.17.0 (excluding security fix releases 2.3.2 and 2.12.4) are vulnerable to an attack where an attacker with permission to modify the logging configuration file can construct a malicious configuration using a JDBC Appender with a data source referencing a JNDI URI which can execute remote code. This issue is fixed by limiting JNDI data source names to the java protocol in Log4j2 versions 2.17.1, 2.12.4, and 2.3.2. # Affected packages 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. This issue does not impact default configurations of Log4j2 and requires an attacker to have control over the Log4j2 configuration, which reduces the likelihood of being exploited.
AI coding agents often install or upgrade packages automatically in maven. A medium vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
Apache Log4j2 versions 2.0-beta7 through 2.17.0 (excluding security fix releases 2.3.2 and 2.12.4) are vulnerable to an attack where an attacker with permission to modify the logging configuration file can construct a malicious configuration using a JDBC Appender with a data source referencing a JNDI URI which can execute remote code. This issue is fixed by limiting JNDI data source names to the java protocol in Log4j2 versions 2.17.1, 2.12.4, and 2.3.2. # Affected packages 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. This issue does not impact default configurations of Log4j2 and requires an attacker to have control over the Log4j2 configuration, which reduces the likelihood of being exploited.
Update org.apache.logging.log4j:log4j-core to 2.3.2; org.apache.logging.log4j:log4j-core to 2.12.4; org.apache.logging.log4j:log4j-core to 2.17.1; org.ops4j.pax.logging:pax-logging-log4j2 to 1.9.2; org.ops4j.pax.logging:pax-logging-log4j2 to 1.10.9; org.ops4j.pax.logging:pax-logging-log4j2 to 1.11.13; org.ops4j.pax.logging:pax-logging-log4j2 to 2.0.14 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanImproper Input Validation and Injection in Apache Log4j2 affects org.apache.logging.log4j:log4j-core (maven), org.apache.logging.log4j:log4j-core (maven), org.apache.logging.log4j:log4j-core (maven), org.ops4j.pax.logging:pax-logging-log4j2 (maven), org.ops4j.pax.logging:pax-logging-log4j2 (maven), org.ops4j.pax.logging:pax-logging-log4j2 (maven), org.ops4j.pax.logging:pax-logging-log4j2 (maven). Severity is medium. Apache Log4j2 versions 2.0-beta7 through 2.17.0 (excluding security fix releases 2.3.2 and 2.12.4) are vulnerable to an attack where an attacker with permission to modify the logging configuration file can construct a malicious configuration using a JDBC Appender with a data source referencing a JNDI URI which can execute remote code. This issue is fixed by limiting JNDI data source names to the java protocol in Log4j2 versions 2.17.1, 2.12.4, and 2.3.2. # Affected packages 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. This issue does not impact default configurations of Log4j2 and requires an attacker to have control over the Log4j2 configuration, which reduces the likelihood of being exploited.
AI coding agents often install or upgrade packages automatically in maven. A medium vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| org.apache.logging.log4j:log4j-coremaven | >=2.0-beta7,<2.3.2 | 2.3.2 |
| org.apache.logging.log4j:log4j-coremaven | >=2.4,<2.12.4 | 2.12.4 |
| org.apache.logging.log4j:log4j-coremaven | >=2.13.0,<2.17.1 | 2.17.1 |
| org.ops4j.pax.logging:pax-logging-log4j2maven | >=1.8.0,<1.9.2 | 1.9.2 |
| org.ops4j.pax.logging:pax-logging-log4j2maven | >=1.10.0,<1.10.9 | 1.10.9 |
| org.ops4j.pax.logging:pax-logging-log4j2maven | >=1.11.0,<1.11.13 | 1.11.13 |
| org.ops4j.pax.logging:pax-logging-log4j2maven | >=2.0.0,<2.0.14 | 2.0.14 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard| Package | Affected range | Fixed version |
|---|---|---|
| org.apache.logging.log4j:log4j-coremaven | >=2.0-beta7,<2.3.2 | 2.3.2 |
| org.apache.logging.log4j:log4j-coremaven | >=2.4,<2.12.4 | 2.12.4 |
| org.apache.logging.log4j:log4j-coremaven | >=2.13.0,<2.17.1 | 2.17.1 |
| org.ops4j.pax.logging:pax-logging-log4j2maven | >=1.8.0,<1.9.2 | 1.9.2 |
| org.ops4j.pax.logging:pax-logging-log4j2maven | >=1.10.0,<1.10.9 | 1.10.9 |
| org.ops4j.pax.logging:pax-logging-log4j2maven | >=1.11.0,<1.11.13 | 1.11.13 |
| org.ops4j.pax.logging:pax-logging-log4j2maven | >=2.0.0,<2.0.14 | 2.0.14 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard