Fix heap-based buffer overflow in GetReturnCallDropKeepCount by adding checks in OnReturnCallExpr #2689
+3
−0
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 #2557
Root Cause
The interpreter’s
OnReturnCallExprusesfunc_indexto index into its internalfunc_types_vector without proper bounds checking. When areturn_callinstruction references a function index that has not yet been added tofunc_types_, an invalidFuncTypereference is passed toGetReturnCallDropKeepCount, leading to a heap-based buffer overflow when accessingfunc_type.params.Fix
Add explicit bounds checking in
OnReturnCallExprto ensurefunc_index < func_types_.size()before accessingfunc_types_. This prevents invalidFuncTypereferences and eliminates the out-of-bounds read that caused the heap-buffer-overflow.Verification Before Fix
Running the PoC triggers AddressSanitizer error:
Verification After Fix
Running the PoC: