Honeypot contracts via failed-transaction bytecode persistence
Published Feb 8, 2021 · Updated Aug 3, 2024
Cache lifecycle inconsistency in the EVM module of Cosmos Network Ethermint 0.4.0 and earlier allows remote attackers to persist failed bytecode. CommitStateDB retains stateObject.code after a multi-message transaction fails, then writes that stale bytecode to persistent storage during EndBlock. Network access to submit transactions requires no authentication or user interaction, and the resulting state corruption can create deceptive honeypot contracts.
Summary
What happened
Cache lifecycle inconsistency in the EVM module of Cosmos Network Ethermint 0.4.0 and earlier allows remote attackers to persist failed bytecode. CommitStateDB retains stateObject.code after a multi-message transaction fails, then writes that stale bytecode to persistent storage during EndBlock. Network access to submit transactions requires no authentication or user interaction, and the resulting state corruption can create deceptive honeypot contracts.
The record
- CVE
- CVE-2021-25836
- Published
- Feb 8, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 8, 2021CVE 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
No sourced classifications are available.
Public exploit references
- Multi-message transaction cache-persistence reproductionproof 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