Ethermint DoS through Unintended Contract Selfdestruct
evmos ethermint
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/evmos/ethermint Go |
|
|
| github.com/evmos/evmos Go |
|
|
evmos ethermint
| Product | Affected | Fixed in |
|---|---|---|
| github.com/evmos/ethermint Go |
|
|
| github.com/evmos/evmos Go |
|
|
|
|
| github.com/Kava-Labs/kava Go |
|
|
| github.com/evmos/evmos/v2 Go |
| No fix yet |
| github.com/evmos/evmos/v3 Go |
| No fix yet |
| github.com/evmos/evmos/v4 Go |
| No fix yet |
| github.com/evmos/evmos/v5 Go |
| No fix yet |
| github.com/evmos/evmos/v6 Go |
| No fix yet |
| github.com/evmos/evmos/v7 Go |
|
|
| github.com/kava-labs/kava Go |
|
|
Ethermint is an Ethereum library. In Ethermint running versions before `v0.17.2`, the contract `selfdestruct` invocation permanently removes the corresponding bytecode from the internal database storage. However, due to a bug in the `DeleteAccount`function, all contracts that used the identical bytecode (i.e shared the same `CodeHash`) will also stop working once one contract invokes `selfdestruct`, even though the other contracts did not invoke the `selfdestruct` OPCODE. This vulnerability has been patched in Ethermint version v0.18.0. The patch has state machine-breaking changes for applications using Ethermint, so a coordinated upgrade procedure is required. A workaround is available. If a contract is subject to DoS due to this issue, the user can redeploy the same contract, i.e. with identical bytecode, so that the original contract's code is recovered. The new contract deployment restores the `bytecode hash -> bytecode` entry in the internal state.
From the CVE record · GitHub_M
In affected Ethermint versions, a contract invoking selfdestruct can remove bytecode needed by other contracts with the same CodeHash, causing those contracts to stop working. This can result in denial of service even though the other contracts did not invoke selfdestruct. The input does not specify network access, authentication, or user-interaction requirements.
Engineers running the listed Go packages should check versions below their stated fixes; all listed evmos/v2 through evmos/v6 versions are affected and have no listed fix.