Contract-data exposure and corruption via slice overflow
Published Feb 1, 2024 · Updated Jun 17, 2025
Out-of-bounds access in Vyper 0.3.10 and earlier allows remote attackers to read or corrupt contract data through crafted slice arguments. The built-in slice runtime check adds nonliteral start and length values without detecting uint256 overflow, so a wrapped sum passes the source-length comparison. Reachability requires a compiled contract to pass attacker-controlled nonliteral values to slice; exploitation can expose storage, memory, or calldata or corrupt an array length.
Summary
What happened
Out-of-bounds access in Vyper 0.3.10 and earlier allows remote attackers to read or corrupt contract data through crafted slice arguments. The built-in slice runtime check adds nonliteral start and length values without detecting uint256 overflow, so a wrapped sum passes the source-length comparison. Reachability requires a compiled contract to pass attacker-controlled nonliteral values to slice; exploitation can expose storage, memory, or calldata or corrupt an array length.
The record
- CVE
- CVE-2024-24561
- Published
- Feb 1, 2024
- Updated
- Jun 17, 2025
- Vendor
- Vyper
- Product
- Vyper
- Classifications
- CWE-787, CWE-119, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 1, 2024CVE publishedPublication date reported by the CVE source.
- Jun 17, 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.10
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Upstream slice overflow proof of conceptproof 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