fix(psd): avoid signed overflow computing layer/mask extents#5306
Open
lgritz wants to merge 1 commit into
Open
fix(psd): avoid signed overflow computing layer/mask extents#5306lgritz wants to merge 1 commit into
lgritz wants to merge 1 commit into
Conversation
read_layer_record computed a layer's width/height as std::abs((int)right - (int)left). The rectangle coordinates are signed 32-bit values (layers can have negative offsets), but were stored in unsigned (uint32_t) struct fields, and subtracting two ints near the extremes overflows -- undefined behavior that UBSan flagged on a fuzzed file (1615681375 - -1605526113 cannot be represented in type 'int'). Retype Layer's and MaskData's top/left/bottom/right fields as int32_t, matching what they actually hold, instead of reinterpreting bits at the point of use. Widen to int64_t before subtracting so the computation can't overflow; the absolute difference of two int32 values always fits in uint32, and validate_resolution still rejects implausibly large extents. The mask data rect (used for layer masks) had the identical std::abs((int)right - (int)left) overflow hazard in load_layer_channel and gets the same fix. Assisted-by: Claude Code / Sonnet 5 Signed-off-by: Larry Gritz <lg@larrygritz.com>
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.
read_layer_record computed a layer's width/height as std::abs((int)right - (int)left). The rectangle coordinates are signed 32-bit values (layers can have negative offsets), but were stored in unsigned (uint32_t) struct fields, and subtracting two ints near the extremes overflows -- undefined behavior that UBSan flagged on a fuzzed file (1615681375 - -1605526113 cannot be represented in type 'int').
Retype Layer's and MaskData's top/left/bottom/right fields as int32_t, matching what they actually hold, instead of reinterpreting bits at the point of use. Widen to int64_t before subtracting so the computation can't overflow; the absolute difference of two int32 values always fits in uint32, and validate_resolution still rejects implausibly large extents.
The mask data rect (used for layer masks) had the identical std::abs((int)right - (int)left) overflow hazard in load_layer_channel and gets the same fix.
Assisted-by: Claude Code / Sonnet 5