[GHSA-qv9r-c865-cp47] Improper encoding of non-finite floating-point values...#8693
Open
ppkarwasz wants to merge 1 commit into
Open
[GHSA-qv9r-c865-cp47] Improper encoding of non-finite floating-point values...#8693ppkarwasz wants to merge 1 commit into
ppkarwasz wants to merge 1 commit into
Conversation
github-actions
Bot
changed the base branch from
main
to
ppkarwasz/advisory-improvement-8693
Contributor
There was a problem hiding this comment.
Pull request overview
Restores detailed metadata for the Apache Log4j API advisory.
Changes:
- Adds affected Maven version ranges and summary.
- Updates CVSS v4, description, and source reference.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| ], | ||
| "details": "Improper encoding of non-finite floating-point values during MapMessage JSON serialization in Apache Log4j API produces output that is not valid JSON. This issue affects Apache Log4j API versions 2.13.1 through 2.25.4 and version 2.26.0.\n\nThe fix for CVE-2026-34481 did not cover all code paths: when a MapMessage contains a non-finite IEEE 754 value (NaN, Infinity, or -Infinity), MapMessage.asJson() emits the corresponding bare token. RFC 8259 does not permit these tokens, so a conformant parser rejects the resulting document.\n\nThe defect is reachable only when both of the following conditions hold:\n\n * The application uses the message resolver https://logging.apache.org/log4j/2.x/manual/json-template-layout.html#event-template-resolver-message of JsonTemplateLayout or any other layout that relies on MapMessage.asJson() or MapMessage.getFormattedMessage(new String[]{\"JSON\"}).\n * The application logs a MapMessage that contains an attacker-controlled floating-point value.\n\n\nAn attacker who can supply a non-finite value can cause the affected layout to emit malformed JSON, which may corrupt the enclosing log record or disrupt downstream log ingestion and parsing.\n\nUsers are advised to upgrade to Apache Log4j API 2.25.5 or 2.26.1, both of which emit RFC 8259-compliant JSON for non-finite values.", | ||
| "summary": "Apache Log4j API: Improper serialization of non-finite floating-point values in `MapMessage.asJson()`", | ||
| "details": "Improper encoding of non-finite floating-point values during `MapMessage` JSON serialization in Apache Log4j API produces output that is not valid JSON. This issue affects Apache Log4j API versions 2.13.1 through 2.25.4 and version 2.26.0.\n\nThe fix for CVE-2026-34481 did not cover all code paths: when a `MapMessage` contains a non-finite IEEE 754 value (`NaN`, `Infinity`, or `-Infinity`), `MapMessage.asJson()` emits the corresponding bare token. RFC 8259 does not permit these tokens, so a conformant parser rejects the resulting document.\n\nThe defect is reachable only when both of the following conditions hold:\n\n * The application uses the [`message` resolver](https://logging.apache.org/log4j/2.x/manual/json-template-layout.html#event-template-resolver-message) of `JsonTemplateLayout` or any other layout that relies on `MapMessage.asJson()` or `MapMessage.getFormattedMessage(new String[]{\"JSON\"})`.\n * The application logs a `MapMessage` that contains an attacker-controlled floating-point value.\n\n\nAn attacker who can supply a non-finite value can cause the affected layout to emit malformed JSON, which may corrupt the enclosing log record or disrupt downstream log ingestion and parsing.\n\nUsers are advised to upgrade to Apache Log4j API 2.25.5 or 2.26.1, both of which emit RFC 8259-compliant JSON for non-finite values.", |
Author
There was a problem hiding this comment.
I don't think it is worth cluttering the description with pre-release versions. Alpha and beta versions of Log4j are not meant to be used in production.
| "url": "https://github.com/apache/logging-log4j2/pull/4163" | ||
| }, | ||
| { | ||
| "type": "WEB", |
Author
There was a problem hiding this comment.
This is what the UI chose to insert.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates
Comments
Restore data lost during MITRE -> NVD -> GitHub Advisories conversions.