fix: add bounds check before memcpy in verbs.c#11478
Open
orbisai0security wants to merge 2 commits into
Open
Conversation
Automated security fix generated by OrbisAI Security
The allocation size calculation at verbs
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.
Summary
Fix high severity security issue in
contrib/ibmock/verbs.c.Vulnerability
V-004contrib/ibmock/verbs.c:152Description: The allocation size calculation at verbs.c:152 multiplies sizeof(*recv_wr->sge) by wr->num_sge without overflow checking. If wr->num_sge is attacker-controlled and sufficiently large, the multiplication overflows to a small value, causing an undersized allocation. The subsequent memcpy at line 163 then writes the full (non-overflowed) amount of data beyond the buffer boundary, causing heap corruption.
Changes
contrib/ibmock/verbs.cVerification
Security Invariant
Regression test
This test guards against regressions — it's useful independent of the code change above.
Automated security fix by OrbisAI Security