GH-47740: [C++][Parquet] Fix undefined behavior when reading invalid Parquet data#47741
Merged
pitrou merged 2 commits intoapache:mainfrom Oct 8, 2025
Merged
GH-47740: [C++][Parquet] Fix undefined behavior when reading invalid Parquet data#47741pitrou merged 2 commits intoapache:mainfrom
pitrou merged 2 commits intoapache:mainfrom
Conversation
Member
Author
|
@github-actions crossbow submit -g cpp |
Member
Author
|
@AntoinePrv Would you like to take a look? |
pitrou
commented
Oct 7, 2025
| // There may be remaining null if they are not greedily filled by either decoder calls | ||
| check_and_handle_fully_null_remaining(); | ||
|
|
||
| ARROW_DCHECK(batch.is_done() || exhausted()); |
Member
Author
There was a problem hiding this comment.
This check could trigger if the RLE-bit-packed data is invalid (for example a run of invalid size). @AntoinePrv
pitrou
changed the title
|
Revision: d620685 Submitted crossbow builds: ursacomputing/crossbow @ actions-0059c16459
|
github-actions
bot
added
awaiting committer review
Member
Author
|
Valgrind failure is unrelated and will be fixed by #47743 |
adamreeve
approved these changes
Oct 7, 2025
wgtmac
approved these changes
Oct 8, 2025
|
After merging your PR, Conbench analyzed the 2 benchmarking runs that have been run so far on merge-commit 33d1f32. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. It also includes information about 7 possible false positives for unstable benchmarks that are known to sometimes produce them. |
raulcd
pushed a commit
that referenced
this pull request
Oct 8, 2025
…Parquet data (#47741) ### Rationale for this change Fix issues found by OSS-Fuzz when invalid Parquet data is fed to the Parquet reader: * https://issues.oss-fuzz.com/issues/447262173 * https://issues.oss-fuzz.com/issues/447480433 * https://issues.oss-fuzz.com/issues/447490896 * https://issues.oss-fuzz.com/issues/447693724 * https://issues.oss-fuzz.com/issues/447693728 * https://issues.oss-fuzz.com/issues/449498800 ### Are these changes tested? Yes, using the updated fuzz regression files from apache/arrow-testing#115 ### 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.) * GitHub Issue: #47740 Authored-by: Antoine Pitrou <[email protected]> Signed-off-by: Antoine Pitrou <[email protected]>
mapleFU
reviewed
Oct 10, 2025
| typename EncodingTraits<DType>::Accumulator* out, | ||
| int* out_num_values) { | ||
| std::vector<ByteArray> values(num_values); | ||
| std::vector<ByteArray> values(num_values - null_count); |
Member
Author
There was a problem hiding this comment.
Well, this was not a problem in itself, it was just allocating too much memory :)
zanmato1984
pushed a commit
to zanmato1984/arrow
that referenced
this pull request
Oct 15, 2025
…valid Parquet data (apache#47741) ### Rationale for this change Fix issues found by OSS-Fuzz when invalid Parquet data is fed to the Parquet reader: * https://issues.oss-fuzz.com/issues/447262173 * https://issues.oss-fuzz.com/issues/447480433 * https://issues.oss-fuzz.com/issues/447490896 * https://issues.oss-fuzz.com/issues/447693724 * https://issues.oss-fuzz.com/issues/447693728 * https://issues.oss-fuzz.com/issues/449498800 ### Are these changes tested? Yes, using the updated fuzz regression files from apache/arrow-testing#115 ### 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.) * GitHub Issue: apache#47740 Authored-by: Antoine Pitrou <[email protected]> Signed-off-by: Antoine Pitrou <[email protected]>
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
5 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.
Rationale for this change
Fix issues found by OSS-Fuzz when invalid Parquet data is fed to the Parquet reader:
Are these changes tested?
Yes, using the updated fuzz regression files from apache/arrow-testing#115
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.)