CriticalGHSA-xxfh-x98p-j8fr

Remote code injection in Log4j (through pax-logging-log4j2)

Published 10 Dec 2021 · Updated 2 Dec 2024

Is your project on an affected org.ops4j.pax.logging:pax-logging-log4j2?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=2.0.0 <2.0.11
Fixed in
2.0.11
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.ops4j.pax.logging:pax-logging-log4j2 -DdepVersion=2.0.11 -DforceVersion=true
Affected
<1.11.10
Fixed in
1.11.10
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.ops4j.pax.logging:pax-logging-log4j2 -DdepVersion=1.11.10 -DforceVersion=true

Details

Impact

Remote Code Execution.

Patches

Users of pax-logging 1.11.9 should update to 1.11.10. Users of pax-logging 2.0.10 should update to 2.0.11.

Workarounds

Set system property -Dlog4j2.formatMsgNoLookups=true

References

https://github.com/advisories/GHSA-jfh8-c2jp-5v3q

Is GHSA-xxfh-x98p-j8fr in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.ops4j.pax.logging:pax-logging-log4j2, and gives you the command that fixes it.

More advisories for org.ops4j.pax.logging:pax-logging-log4j2

  • MediumCVE-2021-44832Improper Input Validation and Injection in Apache Log4j2 · 4 Jan 2022
  • HighCVE-2021-45105Apache Log4j2 vulnerable to Improper Input Validation and Uncontrolled Recursion · 18 Dec 2021
  • CriticalCVE-2021-45046Incomplete fix for Apache Log4j vulnerability · 14 Dec 2021
  • CriticalCVE-2021-44228Remote code injection in Log4j · 10 Dec 2021
org.ops4j.pax.logging:pax-logging-log4j2 security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.