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

Severity: info ยท Published 2021-12-10

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

Technologies: org.ops4j.pax.logging:pax-logging-log4j2 (Maven). Vendors: Maven.

Quick answers

Is This vulnerability exploited in the wild?
No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?
Informational severity, published 10 December 2021.
Which products and versions are affected?
org.ops4j.pax.logging:pax-logging-log4j2 (Maven) ECOSYSTEM:introduced=2.0.0,fixed=2.0.11.
Is there a fix for This vulnerability?
Yes. org.ops4j.pax.logging:pax-logging-log4j2 (Maven): upgrade to 2.0.11 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected?
Check whether you run org.ops4j.pax.logging:pax-logging-log4j2 (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.ops4j.pax.logging:pax-logging-log4j2 (Maven): upgrade to 2.0.11 or later
    # set org.ops4j.pax.logging:pax-logging-log4j2 to 2.0.11 in your pom.xml or build.gradle

Affected products

  • org.ops4j.pax.logging:pax-logging-log4j2 (Maven) ECOSYSTEM:introduced=2.0.0,fixed=2.0.11

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.