Incomplete fix for Apache Log4j vulnerability
What to do
- Upgrade to a fixed version: org.apache.logging.log4j:log4j-core 2.16.0, org.ops4j.pax.logging:pax-logging-log4j2 1.9.2, org.ops4j.pax.logging:pax-logging-log4j2 1.10.8, org.ops4j.pax.logging:pax-logging-log4j2 1.11.11 (see table).
- This is exploited in the wild: treat it as urgent (CISA's federal deadline is May 22, 2023).
- Redeploy and restart long-running processes so they load the fixed code.
Affected packages
org.apache.logging.log4j:log4j-core
- >= 2.13.0, < 2.16.0
- 2.16.0
Check your project: mvn dependency:tree -Dincludes=org.apache.logging.log4j:log4j-core
org.ops4j.pax.logging:pax-logging-log4j2
- >= 1.8.0, < 1.9.2
- 1.9.2
Check your project: mvn dependency:tree -Dincludes=org.ops4j.pax.logging:pax-logging-log4j2
org.ops4j.pax.logging:pax-logging-log4j2
- >= 1.10.0, < 1.10.8
- 1.10.8
Check your project: mvn dependency:tree -Dincludes=org.ops4j.pax.logging:pax-logging-log4j2
org.ops4j.pax.logging:pax-logging-log4j2
- >= 1.11.0, < 1.11.11
- 1.11.11
Check your project: mvn dependency:tree -Dincludes=org.ops4j.pax.logging:pax-logging-log4j2
org.ops4j.pax.logging:pax-logging-log4j2
- >= 2.0.0, < 2.0.12
- 2.0.12
Check your project: mvn dependency:tree -Dincludes=org.ops4j.pax.logging:pax-logging-log4j2
org.apache.logging.log4j:log4j-core
- >= 2.4.0, < 2.12.2
- 2.12.2
Check your project: mvn dependency:tree -Dincludes=org.apache.logging.log4j:log4j-core
org.apache.logging.log4j:log4j-core
- < 2.3.1
- 2.3.1
Check your project: mvn dependency:tree -Dincludes=org.apache.logging.log4j:log4j-core
What changed
Added to CISA KEV on 2023-05-01: exploitation in the wild confirmed; federal remediation due 2023-05-22.