Vulnerability in Vyperlang Vyper
CVE-2024-32481
Vyper is a pythonic Smart Contract Language for the Ethereum virtual machine. Starting in version 0.3.8 and prior to version 0.4.0b1, when looping over a `range` of the form `range(start, start + N)`, if `start` is negative, the execution will always revert. This issue is caused by an incorrect assertion inserted by the code generation of the range `stmt.parse_For_range()`. The issue arises when `start` is signed, instead of using `sle`, `le` is used and `start` is interpreted as an unsigned integer for the comparison. If it is a negative number, its 255th bit is set to `1` and is hence interpreted as a very large unsigned integer making the assertion always fail. Any contract having a `range(start, start + N)` where `start` is a signed integer with the possibility for `start` to be negative is affected. If a call goes through the loop while supplying a negative `start` the execution will revert. Version 0.4.0b1 fixes the issue.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 5.3 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N.
EPSS exploit prediction
EPSS 0.008, 56.9th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Vyperlang Vyper — versions >= 0.3.8, < 0.4.0b1, 0.4.0
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 1 other repository (fkie-cad/nvd-json-data-feeds). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- https://github.com/vyperlang/vyper/security/advisories/GHSA-ppx5-q359-pvwj (Exploit, Vendor Advisory)
- https://github.com/vyperlang/vyper/commit/3de1415ee77a9244eb04bdb695e249d3ec9ed868 (Patch)
- https://github.com/vyperlang/vyper/commit/5319cfbe14951e007ccdb323257e5ada869b35d5 (Patch)
- https://github.com/vyperlang/vyper/blob/9136169468f317a53b4e7448389aa315f90b95ba/vyper/codegen/stmt.py#L286-L287 (Product)