Incorrect contract behavior via overwritten struct buffer
Published Oct 6, 2021 · Updated Aug 4, 2024
Memory corruption in Vyper before 0.3.0 allows attackers to alter compiled contract behavior via a function call inside a literal struct. During literal-struct construction, the compiler points the result at the current stack top, so an embedded private call reuses that memory and overwrites fields. Exposure requires bytecode compiled from a contract whose literal struct evaluates a function call; corrupted return data can change downstream contract logic.
Summary
What happened
Memory corruption in Vyper before 0.3.0 allows attackers to alter compiled contract behavior via a function call inside a literal struct. During literal-struct construction, the compiler points the result at the current stack top, so an embedded private call reuses that memory and overwrites fields. Exposure requires bytecode compiled from a contract whose literal struct evaluates a function call; corrupted return data can change downstream contract logic.
The record
- CVE
- CVE-2021-41121
- Published
- Oct 6, 2021
- Updated
- Aug 4, 2024
- Vendor
- Vyper
- Product
- Vyper
- Classifications
- CWE-119
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 6, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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.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
No public exploit references are available in this record.
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