Incorrect contract behavior via unchecked range iterator
Published May 11, 2023 · Updated Jan 24, 2025
Integer overflow in Vyper before 0.3.8 allows attackers to trigger incorrect values in contracts compiled from affected range loops. The _parse_For_range code generator emitted range(a, a + N) iteration without clamping the start against the iterator type's upper bound. Exploitation requires that loop form near the type maximum; the resulting contract can store an out-of-range value and execute incorrect logic.
Summary
What happened
Integer overflow in Vyper before 0.3.8 allows attackers to trigger incorrect values in contracts compiled from affected range loops. The _parse_For_range code generator emitted range(a, a + N) iteration without clamping the start against the iterator type's upper bound. Exploitation requires that loop form near the type maximum; the resulting contract can store an out-of-range value and execute incorrect logic.
The record
- CVE
- CVE-2023-32058
- Published
- May 11, 2023
- Updated
- Jan 24, 2025
- Vendor
- Vyper
- Product
- Vyper
- Classifications
- CWE-190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 11, 2023CVE publishedPublication date reported by the CVE source.
- Jan 24, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.3.8
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Range-loop overflow demonstrationproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo