github.com/crypto-org-chain/cronos
Affected
- introduced
0, fixed0.8.0(semver)
Fixed versions
0.8.0
Fix
- Fixed version
0.8.0go get github.com/crypto-org-chain/[email protected]
Advisory
Also known as: GO-2022-0829
Cronos vulnerable to DoS through unintended Contract Selfdestruct
In Cronos nodes running versions before v0.7.0, the contract selfdestruct invocation permanently removes the corresponding bytecode from the internal database storage. However, due to a bug in Ethermint, 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. Thanks to the successfully coordinated security vulnerability disclosure, no smart contracts were impacted through the use of this vulnerability. Smart contract states and storage values are not affected by this vulnerability. This problem has been patched in Cronos v0.8.0. The patch has state machine-breaking changes and the required coordinated network upgrade was done on the block height 3982500 on the Cronos mainnet beta network. 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.
High Basis: The source's own band: HIGH
0, fixed 0.8.0 (semver)0.8.0
0.8.0go get github.com/crypto-org-chain/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0