org.ops4j.pax.logging:pax-logging-log4j2 vulnerabilities
Pax Logging backend implementation based on Apache Log4J2. It provides Log4J2 specific implementation of PaxLoggingService interface and Log4J2 specific configuration methods. Users may customize Log4J2 behaviour (appenders, layouts) by creating fragment attached to this bundle.
- Registry
- Maven
- Latest
- 2.3.5
5 known advisories
The latest version, 2.3.5, is not affected by any of them. Projects on older versions may be.
mvn versions:use-dep-version -Dincludes=org.ops4j.pax.logging:pax-logging-log4j2 -DdepVersion=2.3.5 -DforceVersion=trueIs your project on an affected org.ops4j.pax.logging:pax-logging-log4j2?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for org.ops4j.pax.logging:pax-logging-log4j2
Improper Input Validation and Injection in Apache Log4j2
- Affected
- >=1.8.0 <1.9.2 · >=1.10.0 <1.10.9 · >=1.11.0 <1.11.13 · >=2.0.0 <2.0.14
- Fixed in
- 1.9.2, 1.10.9, 1.11.13, 2.0.14
Apache Log4j2 vulnerable to Improper Input Validation and Uncontrolled Recursion
- Affected
- >=1.8.0 <1.9.2 · >=1.10.0 <1.10.9 · >=1.11.0 <1.11.12 · >=2.0.0 <2.0.13
- Fixed in
- 1.9.2, 1.10.9, 1.11.12, 2.0.13
Incomplete fix for Apache Log4j vulnerability
- Affected
- >=1.8.0 <1.9.2 · >=1.10.0 <1.10.8 · >=1.11.0 <1.11.11 · >=2.0.0 <2.0.12
- Fixed in
- 1.9.2, 1.10.8, 1.11.11, 2.0.12
Remote code injection in Log4j (through pax-logging-log4j2)
- Affected
- >=2.0.0 <2.0.11 · <1.11.10
- Fixed in
- 1.11.10, 2.0.11
Remote code injection in Log4j
- Affected
- >=1.8.0 <1.9.2 · >=1.10.0 <1.10.8 · >=1.11.0 <1.11.10 · >=2.0.0 <2.0.11
- Fixed in
- 1.9.2, 1.10.8, 1.11.10, 2.0.11
Is your org.ops4j.pax.logging:pax-logging-log4j2 version vulnerable?
- org.ops4j.pax.logging:pax-logging-log4j2 2.3No known advisories in 2.3.5
- org.ops4j.pax.logging:pax-logging-log4j2 2.2No known advisories in 2.2.14
- org.ops4j.pax.logging:pax-logging-log4j2 2.1No known advisories in 2.1.4
- org.ops4j.pax.logging:pax-logging-log4j2 2.0No known advisories in 2.0.19
- org.ops4j.pax.logging:pax-logging-log4j2 1.12No known advisories in 1.12.18
- org.ops4j.pax.logging:pax-logging-log4j2 1.11No known advisories in 1.11.17
- org.ops4j.pax.logging:pax-logging-log4j2 1.101 advisory in 1.10.10
- org.ops4j.pax.logging:pax-logging-log4j2 1.91 advisory in 1.9.2
- org.ops4j.pax.logging:pax-logging-log4j2 1.85 advisories in 1.8.7
Which of your client projects still run an old org.ops4j.pax.logging:pax-logging-log4j2?
NPMscan reads the pom.xml, build.gradle and gradle.lockfile in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Maven packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Maven registry.