Reject negative size in mergeDelimitedFrom#28097
Closed
TristanInSec wants to merge 1 commit into
Closed
Conversation
readRawVarint32 returns a negative int for 5-byte varints encoding values >= 2^31. mergeDelimitedFrom passes this directly to LimitedInputStream, which treats negative limits as EOF. This silently produces an empty message and leaves the actual body bytes unconsumed, desynchronizing subsequent parseDelimitedFrom calls on the same stream. Add a negative size check before constructing LimitedInputStream.
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.
Summary
mergeDelimitedFrompasses the return value ofreadRawVarint32directly toLimitedInputStreamwithout checking for negative values. For 5-byte varints encoding values >= 2^31,readRawVarint32returns a negative int (e.g.,\x80\x80\x80\x80\x08decodes to -2147483648).LimitedInputStreamwith a negative limit immediately returns EOF (if (limit <= 0) return -1), causing the parser to produce a default/empty message and returntrue(success). The actual message body bytes remain unconsumed in the stream, permanently desynchronizing subsequentparseDelimitedFromcalls.Fix
Add
if (size < 0) throw InvalidProtocolBufferException.negativeSize()before constructingLimitedInputStream.Test plan
negativeSizeexception thrown