Incorrect contract execution via reversed operand evaluation
Published Sep 4, 2023 · Updated Nov 19, 2024
Incorrect code generation in Vyper 0.4.0 and earlier allows remote attackers to alter contract behavior through affected expressions. The compiler evaluates operands right to left in specified built-ins and operators, so a state-changing operand can precede a dependent read and generate unintended semantics. Exploitation requires a contract compiled by an affected release to use one of those expressions with interdependent side effects; invoking that path can change contract state or results.
Summary
What happened
Incorrect code generation in Vyper 0.4.0 and earlier allows remote attackers to alter contract behavior through affected expressions. The compiler evaluates operands right to left in specified built-ins and operators, so a state-changing operand can precede a dependent read and generate unintended semantics. Exploitation requires a contract compiled by an affected release to use one of those expressions with interdependent side effects; invoking that path can change contract state or results.
The record
- CVE
- CVE-2023-40015
- Published
- Sep 4, 2023
- Updated
- Nov 19, 2024
- Vendor
- Vyper
- Product
- Vyper
- Classifications
- CWE-670
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 4, 2023CVE publishedPublication date reported by the CVE source.
- Nov 19, 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.4.0
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 side-effect ordering 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