THRIFT-6131: Bound Ruby HeaderTransport varint32 parsing - #3687
Merged
Conversation
Client: rb Co-Authored-By: OpenAI Codex (GPT-5.6) <codex@openai.com>
Jens-G
self-requested a review
July 29, 2026 21:11
Jens-G
approved these changes
Jul 29, 2026
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.
Ruby HeaderTransport previously continued parsing malformed variable-length uint32s until the Header boundary. It now limits the reader to five bytes, rejects fifth-byte overflow, and retains valid five-byte values. The regression coverage includes the boundary-sized continuation header, a fifth-byte overflow, and a valid fifth byte.
[skip ci]anywhere in the commit message to free up build resources.