Repository navigation
Guard the second buffer write in parseComment (3.x) - #111
Merged
Merged
Conversation
slachiewicz
added
bug
slachiewicz
marked this pull request as ready for review
November 8, 2026 14:25
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.
Port of #110 to the 3.x line: the second
pc[pcEnd++]write inMXParser.parseComment, for the low surrogate of a supplementary character, lacked the capacity check the first write has, so a comment ending exactly at the buffer boundary threwArrayIndexOutOfBoundsException. Fixes #103 on 3.x.Verified:
mvn -B verifyon JDK 17 → green, including the new boundary test.