Apache Log4j's JsonTemplateLayout https://logging.apache.org/log4j/2.x/manual/json-template-layout.html , in versions up to and including 2.25.3, produces invalid JSON output when log events contain non-finite floating-point values (NaN, Infinity, or -Infinity), which are prohibited by RFC 8259. This may cause downstream log processing systems to reject or fail to index affected records. An attacker can exploit this issue only if both of the following conditions are met: * The application uses JsonTemplateLayout. * The application logs a MapMessage containing an attacker-controlled floating-point value. Users are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue.
| Vendor | Product | Versions |
|---|---|---|
| apache software foundation | apache log4j json template layout | maven/org.apache.logging.log4j:log4j-layout-template-json: >= 2.14.0, < 2.25.4, maven/org.apache.logging.log4j:log4j-layout-template-json: >= 3.0.0-alpha1, < 3.0.0-beta3 |
Downstream vendors/products affected by this vulnerability
| Vendor | Product | Source | Confidence |
|---|---|---|---|
| maven | org.apache.logging.log4j:log4j-layout-template-json | GHSA | 85% |
Updated description with new details, changed severity to HIGH, added CVSS estimate of 7.5, and included new CWE-20.
Initial creation
