Apache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3 and 2.3.1) did not protect from uncontrolled recursion from self-referential lookups. This allows an attacker with control over Thread Context Map data to cause a denial of service when a crafted string is interpreted. This issue was fixed in Log4j 2.17.0, 2.12.3, and 2.3.1.
| Package (Ecosystem) | Introduced | Fixed | Limit |
|---|---|---|---|
| org.apache.logging.log4j:log4j-core(Maven) | 2.4.0 | 2.12.3 | N/A |
| org.apache.logging.log4j:log4j-core(Maven) | 2.13.0 | 2.17.0 | N/A |
| org.apache.logging.log4j:log4j-core(Maven) | 0 | 2.3.1 | N/A |
| org.ops4j.pax.logging:pax-logging-log4j2(Maven) | 1.8.0 | 1.9.2 | N/A |
| org.ops4j.pax.logging:pax-logging-log4j2(Maven) | 1.10.0 | 1.10.9 | N/A |
| org.ops4j.pax.logging:pax-logging-log4j2(Maven) | 1.11.0 | 1.11.12 | N/A |
| org.ops4j.pax.logging:pax-logging-log4j2(Maven) | 2.0.0 | 2.0.13 | N/A |
CVSS Metrics
