Skip to content

Conversation

@simonresch
Copy link
Contributor

When parsing protobuf messages from libfuzzer bytes in the protobuf mutator we don't enforce length limits. This could lead to maxSizeIncrease < 0 situations if the e.g. a String read by the protobuf mutator exceeds the size limit.
To guard against similar cases we now enforce the size constraints for the byte array that is being mutated before performing the mutation.

@simonresch simonresch force-pushed the CIF-1814-fix-possible-negative-size-increase branch from 13f0274 to 935705d Compare October 29, 2025 10:37
When parsing protobuf messages from libfuzzer bytes in the protobuf
mutator we don't enforce length limits. This could lead to
maxSizeIncrease < 0 situations if the e.g. a String read by the protobuf
mutator exceeds the size limit.
To guard against similar cases we now enforce the size constraints for
the byte array that is being mutated before performing the mutation.
@simonresch simonresch force-pushed the CIF-1814-fix-possible-negative-size-increase branch from 935705d to 00f03d5 Compare October 29, 2025 10:38
@simonresch simonresch marked this pull request as ready for review October 29, 2025 10:41
Copy link
Contributor

@oetr oetr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@simonresch simonresch merged commit 6da8018 into main Oct 29, 2025
9 checks passed
@simonresch simonresch deleted the CIF-1814-fix-possible-negative-size-increase branch October 29, 2025 13:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants