UNKNOWN PyPI
Vyper: Memory corruption using function calls within tuples / nested calls
GHSA-2r3x-4mrv-mcxf · CVE-2020-37286
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 performing a function call inside a tuple or as an argument inside another function call, there is a memory corruption issue that occurs because of an incorrect pointer to the the tip of the stack.
Example code:
@internal
def _foo(a: uint256, b: uint256, c: uint256) -> (uint256, uint256, uint256, uint256, uint256):
return 1, a, b, c, 5
@internal
def _foo2() -> uint256:
a: uint256[10] = [6,7,8,9,10,11,12,13,15,16]
return 4
@external
def foo() -> (uint256, uint256, uint256, uint256, uint256):
return self._foo(2, 3, self._foo2())
Please see #2186 for further information
Patches
This problem was fixed in #2186, and released as a part of v0.2.6.
References
- WEB https://github.com/vyperlang/vyper/security/advisories/GHSA-2r3x-4mrv-mcxf
- WEB https://github.com/vyperlang/vyper/pull/2186
- WEB https://github.com/vyperlang/vyper/commit/74ba67d4bec5f8be4f05759e37d2bfb1463e0441
- 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