Contract state corruption via repeated argument evaluation
Published Apr 25, 2024 · Updated Aug 2, 2024
Code-generation error in Vyper 0.3.10 and earlier allows remote attackers to repeat contract side effects through crafted calls. The create_from_blueprint _build_create_IR path fails to cache a side-effecting args expression when raw_args=True, so generated bytecode evaluates it more than once. Exposure requires a compiled contract to use that option with side-effecting arguments; the upstream search found no vulnerable production contracts.
Summary
What happened
Code-generation error in Vyper 0.3.10 and earlier allows remote attackers to repeat contract side effects through crafted calls. The create_from_blueprint _build_create_IR path fails to cache a side-effecting args expression when raw_args=True, so generated bytecode evaluates it more than once. Exposure requires a compiled contract to use that option with side-effecting arguments; the upstream search found no vulnerable production contracts.
The record
- CVE
- CVE-2024-32647
- Published
- Apr 25, 2024
- Updated
- Aug 2, 2024
- Vendor
- Vyper
- Product
- Vyper
- Classifications
- CWE-95
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 25, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 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=*
- 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 boa double-evaluation 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