Compiler crash via misclassified state-variable assignment
Published Jun 22, 2022 · Updated Aug 3, 2024
Reachable assertion in Ethereum Solidity 0.8.14 allows local users to crash solc via a crafted contract processed by SMTChecker. The assignment classifier fails to unwrap a tuple-wrapped qualified state variable, treats it as generic member access, and reaches an internal assertion. A user must compile the crafted source with SMTChecker enabled; the bounded consequence is termination of that compiler process.
Summary
What happened
Reachable assertion in Ethereum Solidity 0.8.14 allows local users to crash solc via a crafted contract processed by SMTChecker. The assignment classifier fails to unwrap a tuple-wrapped qualified state variable, treats it as generic member access, and reaches an internal assertion. A user must compile the crafted source with SMTChecker enabled; the bounded consequence is termination of that compiler process.
The record
- CVE
- CVE-2022-33069
- Published
- Jun 22, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-617
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 22, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- SMTChecker crash reproducerproof 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