Call-data and bytecode corruption via premature msize allocation
Published Sep 18, 2023 · Updated Sep 24, 2024
Memory corruption in Vyper 0.3.4 through 0.3.9 allows remote attackers to alter call data or deployed bytecode via crafted contract calls. The compiler evaluates msize before complex keyword arguments finish writing to memory, allowing those evaluations to overwrite raw_call argument buffers or create-function initcode buffers. Reachability requires clean initial memory, an affected builtin, and complex arguments that write to memory.
Summary
What happened
Memory corruption in Vyper 0.3.4 through 0.3.9 allows remote attackers to alter call data or deployed bytecode via crafted contract calls. The compiler evaluates msize before complex keyword arguments finish writing to memory, allowing those evaluations to overwrite raw_call argument buffers or create-function initcode buffers. Reachability requires clean initial memory, an affected builtin, and complex arguments that write to memory.
The record
- CVE
- CVE-2023-42443
- Published
- Sep 18, 2023
- Updated
- Sep 24, 2024
- Vendor
- Vyper
- Product
- Vyper
- Classifications
- CWE-787
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 18, 2023CVE publishedPublication date reported by the CVE source.
- Sep 24, 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 <=0.3.9
- Affected versionversion=<= 0.3.9
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 builtin memory-corruption examplesproof 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