Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕ Maven
Not in CISA KEV

Remote code injection in Log4j (through pax-logging-log4j2)GHSA-xxfh-x98p-j8fr

GHSA-xxfh-x98p-j8fr is a remote code execution vulnerability in org.ops4j.pax.logging:pax-logging-log4j2. A fix is available for org.ops4j.pax.logging:pax-logging-log4j2 — see the affected versions and patch details below.

Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Dec 2, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected
☕org.ops4j.pax.logging:pax-logging-log4j2☕org.ops4j.pax.logging:pax-logging-log4j2

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.ops4j.pax.logging:pax-logging-log4j2≥ 2.0.0&&< 2.0.112.0.11org.ops4j.pax.logging:pax-logging-log4j2:2.0.11
☕Mavenorg.ops4j.pax.logging:pax-logging-log4j2all versions1.11.10org.ops4j.pax.logging:pax-logging-log4j2:1.11.10

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.ops4j.pax.logging:pax-logging-log4j2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.ops4j.pax.logging:pax-logging-log4j2 to 2.0.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xxfh-x98p-j8fr is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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
O3 Security · Impact-Aware SCA

Is GHSA-xxfh-x98p-j8fr in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Remote code injection in Log4j (through pax-logging-log4j2)