Incorrect state transitions via lost static context
Published Oct 25, 2022 · Updated Apr 23, 2025
Control-flow error in rust-ethereum Rust EVM before 0.36.0 allows remote attackers to cause incorrect state transitions via STATICCALL. In src/executor/stack/executor.rs, StackExecutor passes the current call's is_static argument to a precompile instead of the inherited static state stored in substate metadata. Exploitation requires a custom stateful precompile that relies on is_static, and the consequence is limited to unintended state changes.
Summary
What happened
Control-flow error in rust-ethereum Rust EVM before 0.36.0 allows remote attackers to cause incorrect state transitions via STATICCALL. In src/executor/stack/executor.rs, StackExecutor passes the current call's is_static argument to a precompile instead of the inherited static state stored in substate metadata. Exploitation requires a custom stateful precompile that relies on is_static, and the consequence is limited to unintended state changes.
The record
- CVE
- CVE-2022-39354
- Published
- Oct 25, 2022
- Updated
- Apr 23, 2025
- Vendor
- rust-ethereum
- Product
- Rust EVM
- Classifications
- CWE-670
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 25, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record 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.36.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