Incorrect event topics via unwrapped raw_log values
Published Apr 25, 2024 · Updated Aug 2, 2024
Incorrect code generation in Vyper 0.3.10 and earlier allows attackers to produce wrong event topics via non-literal raw_log values. RawLog.build_IR omits unwrap_location for memory or storage topic expressions, so code generation passes each variable's pointer instead of its value to the EVM log operation. Affected contracts must invoke raw_log with non-literal topics; downstream client applications that rely on those logs can behave unexpectedly.
Summary
What happened
Incorrect code generation in Vyper 0.3.10 and earlier allows attackers to produce wrong event topics via non-literal raw_log values. RawLog.build_IR omits unwrap_location for memory or storage topic expressions, so code generation passes each variable's pointer instead of its value to the EVM log operation. Affected contracts must invoke raw_log with non-literal topics; downstream client applications that rely on those logs can behave unexpectedly.
The record
- CVE
- CVE-2024-32645
- Published
- Apr 25, 2024
- Updated
- Aug 2, 2024
- Vendor
- Vyper
- Product
- Vyper
- Classifications
- CWE-20
- 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=0 <=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 raw_log 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