GHSA-gwj5-wp6r-5q9f is a high-severity (CVSS 8.2) vulnerability in github.com/crypto-org-chain/cronos. A fix is available for github.com/crypto-org-chain/cronos — see the affected versions and patch details below.
Cronos vulnerable to DoS through unintended Contract Selfdestruct
Real-World Exposure
github.com/crypto-org-chain/cronosReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/crypto-org-chain/cronos | all versions | 0.8.0go get github.com/crypto-org-chain/cronos@v0.8.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/crypto-org-chain/cronos, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/crypto-org-chain/cronos to 0.8.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gwj5-wp6r-5q9f is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-gwj5-wp6r-5q9f can be triaged on real exposure rather than presence alone.
Tailored to GHSA-gwj5-wp6r-5q9f. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-gwj5-wp6r-5q9f in your dependencies?
O3 Security finds GHSA-gwj5-wp6r-5q9f across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.