GH-47803: [C++][Parquet] Fix read out of bounds on invalid RLE data #47804
+5
−0
Conversation
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
…data Found by OSS-Fuzz, should fix https://issues.oss-fuzz.com/issues/451150486.
|
This is ready for review, but should not be merged before the regression file is added to the arrow-testing repo. @wgtmac @AntoinePrv @adamreeve |
adamreeve
approved these changes
Oct 13, 2025
github-actions
bot
added
awaiting committer review
wgtmac
approved these changes
Oct 14, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
DO NOT MERGE until apache/arrow-testing#116 is merged and this PR updates the arrow-testing submodule.
Rationale for this change
Found by OSS-Fuzz, should fix https://issues.oss-fuzz.com/issues/451150486.
What changes are included in this PR?
Ensure RLE run is within bounds before reading it.
Are these changes tested?
Yes, by fuzz regression test in ASAN/UBSAN build.
Are there any user-facing changes?
No.
This PR contains a "Critical Fix". (If the changes fix either (a) a security vulnerability, (b) a bug that caused incorrect or invalid data to be produced, or (c) a bug that causes a crash (even when the API contract is upheld), please provide explanation. If not, you can remove this.)