Evmos' transaction execution not accounting for all state transition after interaction with precompiles
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 17.0.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
Evmos is a scalable, high-throughput Proof-of-Stake EVM blockchain that is fully compatible and interoperable with Ethereum. Prior to 17.0.0, there is a way to mint arbitrary tokens due to the possibility to have two different states not in sync during the execution of a transaction. The exploit is based on the fact that to sync the Cosmos SDK state and the EVM one, we rely on the `stateDB.Commit()` method. When we call this method, we iterate though all the `dirtyStorage` and, if and only if it is different than the `originStorage`, we set the new state. Setting the new state means we update the Cosmos SDK KVStore. If a contract storage state that is the same before and after a transaction, but is changed during the transaction and can call an external contract after the change, it can be exploited to make the transaction similar to non-atomic. The vulnerability is critical since this could lead to drain of funds through creative SC interactions. The issue has been patched in versions >=V17.0.0.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- evmos evmos
fixed in 17.0.0
- github.com/evmos/evmos/v16Go
fixed in 17.0.0
- github.com/evmos/evmos/v7Go
through 7.0.0
- github.com/evmos/evmos/v6Go
through 6.0.4
- github.com/evmos/evmos/v5Go
through 5.0.0
- github.com/tharsis/evmosGo
through 1.1.3
- github.com/tharsis/evmos/v2Go
through 2.0.2
- github.com/tharsis/evmos/v3Go
through 3.0.3
- github.com/tharsis/evmos/v4Go
through 4.0.2
- github.com/tharsis/evmos/v5Go
through 5.0.1
- github.com/evmos/evmosGo
All versions
- github.com/evmos/evmos/v2Go
All versions
- github.com/evmos/evmos/v3Go
All versions
- github.com/evmos/evmos/v4Go
All versions
- github.com/evmos/evmos/v5Go
All versions
- github.com/evmos/evmos/v6Go
All versions
- github.com/evmos/evmos/v7Go
All versions
- github.com/evmos/evmos/v8Go
All versions
- github.com/evmos/evmos/v9Go
All versions
- github.com/evmos/evmos/v10Go
All versions
- github.com/evmos/evmos/v11Go
All versions
- github.com/evmos/evmos/v12Go
All versions
- github.com/evmos/evmos/v13Go
All versions
- github.com/evmos/evmos/v14Go
All versions
- github.com/evmos/evmos/v15Go
All versions
- github.com/evmos/evmos/v16Go
All versions
- github.com/evmos/evmos/v17Go
fixed in 17.0.0
- github.com/tharsis/evmosGo
All versions
- github.com/tharsis/evmos/v2Go
All versions
- github.com/tharsis/evmos/v3Go
All versions
- github.com/tharsis/evmos/v4Go
All versions
- github.com/tharsis/evmos/v5Go
All versions