GHSA-8489-44mv-ggj8 Improper Input Validation and Injection in Apache Log4j2

• Maven org.apache.logging.log4j:log4j-core: >= 2.0-beta7, < 2.3.2 → fixed in 2.3.2 • Maven org.apache.logging.log4j:log4j-core: >= 2.4, < 2.12.4 → fixed in 2.12.4 • Maven org.apache.logging.log4j:log4j-core: >= 2.13.0, < 2.17.1 → fixed in 2.17.1 • Maven org.ops4j.pax.logging:pax-logging-log4j2: >= 1.8.0, < 1.9.2 → fixed in 1.9.2 • Maven org.ops4j.pax.logging:pax-logging-log4j2: >= 1.10.0, < 1.10.9 → fixed in 1.10.9 • Maven org.ops4j.pax.logging:pax-logging-log4j2: >= 1.11.0, < 1.11.13 → fixed in 1.11.13 • Maven org.ops4j.pax.logging:pax-logging-log4j2: >= 2.0.0, < 2.0.14 → fixed in 2.0.14

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.