fix out-of-bounds iterator in readStringWcharTag (backport #9310)#9360
Merged
Conversation
(cherry picked from commit 0c50266)
kmilos
approved these changes
Jun 22, 2026
Contributor
Author
|
Tick the box to add this pull request to the merge queue (same as
|
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
2 participants
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.
readStringWcharTag() builds its result from FieldBuf.end() - 3, which points before the start of the buffer when length < 2, so the std::string is constructed from an inverted iterator range. A crafted ASF Content_Description with a 1-byte string length reaches it through contentDescription(). Require length >= 2.
This is an automatic backport of pull request #9310 done by Mergify.