stateObject: represents the state of an account and is used to store its updates during a state transition. This is accomplished using two in memory Storage variables: originStorage and dirtyStorageStateDB: it is the general interface to retrieve accounts and holds a map of stateObjects.An external contributor, @iczc, discovered 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.
Below, are described the steps to perform the attack:
originStorage.If the tx is executed correctly, this is what happens at the store level:
dirtyStorage is committed to the KVStore without changing the originStorage.dirtyStorage, it is updated to...17.0.0Exploitability
AV:NAC:LPR:NUI:NScope
S:UImpact
C:NI:HA:H9.1/CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:HOther