pe: validate offset and size in exception data - #538
Open
Dav1dde wants to merge 2 commits into
Open
Conversation
m4b
approved these changes
Aug 30, 2026
m4b
left a comment
m4b
left a comment
Owner
There was a problem hiding this comment.
Ok, looks good to me, seems reasonable! cc @kkent030315
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
2 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.
It's possible that
pe.exception_data.functions()panics because of an out of bounds error. Size and offset are never validated against the total available data.This adds a check in the constructor which validates size and offset to make the panic in
functions()impossible.We did observe a few of these panics in the wild: https://sentry-s4s2.sentry.io/share/issue/acd5bd4bf9c5417c809ba5f7bbccd747/