GHSA-gwj5-wp6r-5q9f

Suggest an improvement
Source
https://github.com/advisories/GHSA-gwj5-wp6r-5q9f
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2022/08/GHSA-gwj5-wp6r-5q9f/GHSA-gwj5-wp6r-5q9f.json
JSON Data
https://api.osv.dev/v1/vulns/GHSA-gwj5-wp6r-5q9f
Aliases
Published
2022-08-11T18:08:57Z
Modified
2024-08-21T15:58:58.877878Z
Severity
  • 8.2 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H CVSS Calculator
Summary
Cronos vulnerable to DoS through unintended Contract Selfdestruct
Details

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.

Database specific
{
    "nvd_published_at": null,
    "cwe_ids": [
        "CWE-668"
    ],
    "severity": "HIGH",
    "github_reviewed": true,
    "github_reviewed_at": "2022-08-11T18:08:57Z"
}
References

Affected packages

Go / github.com/crypto-org-chain/cronos

Package

Name
github.com/crypto-org-chain/cronos
View open source insights on deps.dev
Purl
pkg:golang/github.com/crypto-org-chain/cronos

Affected ranges

Type
SEMVER
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
0.8.0

Database specific

{
    "last_known_affected_version_range": "<= 0.7.0"
}