Vyper: Call stack corruption when passing complex type containing non-base type members as argument
GHSA-4v7v-gqf9-ww2g · CVE-2020-37287
Published · Modified
AI SAST
Find this class of vulnerability in your own code
Corgea's AI-native static analysis detects vulnerabilities like this one across your repositories, ranks them by exploitability, and returns review-ready fixes.
Description
Impact
When we pass a multi-dimensional array (like [[1, 2], [3, 4]]) as an argument to internal/external functions we get incorrect output. This is due to a stack management issue, because it was assumed that the size of each subtype of an array/struct is 32, which is not always correct.
Example code:
@internal
def test_input(arr: int128[2][1], i: int128) -> (int128[2][1], int128):
return arr, i
@external
def test_values(arr: int128[2][1], i: int128) -> (int128[2][1], int128):
return self.test_input(arr, i)
Please see #2183 for further information
Patches
This problem was fixed in #2184, and released as a part of v0.2.6.
References
- WEB https://github.com/vyperlang/vyper/security/advisories/GHSA-4v7v-gqf9-ww2g
- WEB https://github.com/vyperlang/vyper/issues/2183
- WEB https://github.com/vyperlang/vyper/pull/2184
- WEB https://github.com/vyperlang/vyper/commit/0be02b7331e8febe79d5a4218829c72e30417a29
- PACKAGE https://github.com/vyperlang/vyper
- WEB https://github.com/vyperlang/vyper/releases/tag/v0.2.6
Ready to move
Start Securing
Free, no credit card | First findings in minutes