Incorrect bytecode via miscalculated sha3_64 stack height
Published Feb 5, 2024 · Updated Aug 26, 2024
Code-generation error in Vyper 0.3.10 and earlier allows local users to produce incorrect EVM bytecode through hand-written IR. In compile_ir.py, sha3_64 compiles its second argument without incrementing the tracked stack height, causing an incorrect DUP instruction. The flaw is unreachable from ordinary Vyper source compilation and requires direct use of the fang IR compiler, so compiler-generated IR and normally compiled contracts are unaffected.
Summary
What happened
Code-generation error in Vyper 0.3.10 and earlier allows local users to produce incorrect EVM bytecode through hand-written IR. In compile_ir.py, sha3_64 compiles its second argument without incrementing the tracked stack height, causing an incorrect DUP instruction. The flaw is unreachable from ordinary Vyper source compilation and requires direct use of the fang IR compiler, so compiler-generated IR and normally compiled contracts are unaffected.
The record
- CVE
- CVE-2024-24559
- Published
- Feb 5, 2024
- Updated
- Aug 26, 2024
- Vendor
- Vyper
- Product
- Vyper
- Classifications
- CWE-327
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 5, 2024CVE publishedPublication date reported by the CVE source.
- Aug 26, 2024Record 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
- 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 hand-written IR 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