Vyper: Call stack corruption when passing complex type containing non-base type members as argument
### 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: ```python @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`](https://github.com/vyperlang/vyper/releases/tag/v0.2.6).
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2020-37287US | medium5.9 | — | ||
Vyper before 0.2.6 contains a call stack corruption vulnerability that causes incorrect function outputs when complex types with non-base members are passed as arguments. Contracts… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/vyperlang/vyperPACKAGE
- https://github.com/vyperlang/vyper/commit/0be02b7331e8febe79d5a4218829c72e30417a29WEB
- https://github.com/vyperlang/vyper/issues/2183WEB
- https://github.com/vyperlang/vyper/pull/2184WEB
- https://github.com/vyperlang/vyper/releases/tag/v0.2.6WEB
- https://github.com/vyperlang/vyper/security/advisories/GHSA-4v7v-gqf9-ww2gWEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan