wirror800 opened a new issue, #25853: URL: https://github.com/apache/pulsar/issues/25853
### Search before reporting - [x] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar. ### Read release policy - [x] I understand that [unsupported versions](https://pulsar.apache.org/contribute/release-policy/#supported-versions) don't get bug fixes. I will attempt to reproduce the issue on a supported version of Pulsar client and Pulsar broker. ### User environment Broker version: 4.2.1 ### Issue Description 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. Remediation Users are advised to upgrade to Apache Log4j JSON Template Layout version 2.25.4, which corrects this issue. ### Error messages ```text ``` ### Reproducing the issue upgrade to Apache Log4j JSON Template Layout version 2.25.4 ### Additional information _No response_ ### Are you willing to submit a PR? - [ ] I'm willing to submit a PR! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
