Buffer overflow in Vyperlang Vyper
CVE-2024-24560
Vyper is a Pythonic Smart Contract Language for the Ethereum Virtual Machine. When calls to external contracts are made, we write the input buffer starting at byte 28, and allocate the return buffer to start at byte 0 (overlapping with the input buffer). When checking RETURNDATASIZE for dynamic types, the size is compared only to the minimum allowed size for that type, and not to the returned value's length. As a result, malformed return data can cause the contract to mistake data from the input buffer for returndata. When the called contract returns invalid ABIv2 encoded data, the calling contract can read different invalid data (from the dirty buffer) than the called contract returned.
Vulnerability class: Buffer Overflow
EPSS: 0.005 (41.5th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 3.7 (Low). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N.
Affected products
- Vyperlang Vyper — versions <= 0.3.10
Weakness classification (CWE)
Public proof-of-concept exploits
References
- security-advisories@github.com (x_refsource_CONFIRM, Exploit, Vendor Advisory)
Frequently asked questions
- What is CVE-2024-24560?
- CVE-2024-24560 is a low-severity vulnerability in Vyperlang Vyper, classified under Improper Restriction of Operations within the Bounds of a Memory Buffer. CVSS score: 3.7/10. Published 2024-02-02.
- How severe is CVE-2024-24560?
- Low severity. CVSS v3 base score is 3.7 out of 10.
- Is CVE-2024-24560 known to be exploited?
- 1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.