CVE-2024-32644

Source
https://nvd.nist.gov/vuln/detail/CVE-2024-32644
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-32644.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2024-32644
Aliases
Published
2024-04-19T15:15:50Z
Modified
2024-10-08T04:11:21.822310Z
Summary
[none]
Details

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.

References

Affected packages

Git / github.com/evmos/evmos

Affected ranges

Type
GIT
Repo
https://github.com/evmos/evmos
Events
Introduced
0 Unknown introduced commit / All previous commits are affected
Fixed

Affected versions

v16.*

v16.0.0
v16.0.0-rc1
v16.0.0-rc2
v16.0.0-rc2.1
v16.0.0-rc4
v16.0.0-rc5
v16.0.1
v16.0.2
v16.0.3