WorldHeightMap: Add bounds checks for blendNdx to prevent crashes - #126
Open
seer-by-sentry[bot] wants to merge 1 commit into
Open
WorldHeightMap: Add bounds checks for blendNdx to prevent crashes#126seer-by-sentry[bot] wants to merge 1 commit into
seer-by-sentry[bot] wants to merge 1 commit into
Conversation
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.
Fixes CLIENT-TA. The issue was that: Out-of-bounds index read from
m_blendTileNdxesaccessesm_blendedTilesarray without bounds checking, causing an access violation read.blendNdxingetCliffForTileIndexandgetUVForTileIndexForCliffto ensure it's within the valid range ofm_numBlendedTiles.blendNdxis out of bounds, the code now treats it as if there's no blending, preventing potential crashes due to out-of-bounds access.This fix was generated by Seer in Sentry, triggered automatically. 👁️ Run ID: 2587968
Not quite right? Click here to continue debugging with Seer.