{"answers":{"affected":"3 open source packages ship an affected version, including github.com/crypto-org-chain/cronos.","exploited":"There is no known exploitation of GHSA-gwj5-wp6r-5q9f in the wild and no public exploit code.","fix":"Upgrade github.com/crypto-org-chain/cronos to 0.8.0 or later.","what":"GHSA-gwj5-wp6r-5q9f is a denial of service vulnerability in github.com/crypto-org-chain/cronos, published on 11 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-gwj5-wp6r-5q9f and fix it if it is affected.\n\nWhat it is: GHSA-gwj5-wp6r-5q9f is a denial of service vulnerability in github.com/crypto-org-chain/cronos, published on 11 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-gwj5-wp6r-5q9f in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/crypto-org-chain/cronos (Go): affected all versions; fixed in 0.8.0\n- github.com/crypto-org-chain/cronos (Go): affected all versions; fixed in 0.8.0\n- github.com/crypto-org-chain/cronos (Go): affected all versions; fixed in 0.8.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-gwj5-wp6r-5q9f/ (Markdown: https://insights.sbomify.com/GHSA-gwj5-wp6r-5q9f/index.md)","id":"GHSA-gwj5-wp6r-5q9f","markdown":"https://insights.sbomify.com/GHSA-gwj5-wp6r-5q9f/index.md","name":"GHSA-gwj5-wp6r-5q9f","record":{"aliases":["GO-2022-0829"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Cronos blockchain node","requires_auth":"none","summary":"An attacker can cause denial of service for smart contracts sharing identical bytecode by triggering a selfdestruct on one contract, affecting all instances.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"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.","ecosystems":["Go"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Cronos vulnerable to DoS through unintended Contract Selfdestruct","id":"GHSA-gwj5-wp6r-5q9f","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Go","product":null,"products":[],"type":"denial_of_service","year":"2022"},"n_packages":3,"n_references":null,"packages":[{"ecosystem":"Go","fixed":["0.8.0"],"introduced":["0"],"last_affected":[],"package":"github.com/crypto-org-chain/cronos","purl":null,"source":"GHSA-gwj5-wp6r-5q9f"},{"ecosystem":"Go","fixed":["0.8.0"],"introduced":["0"],"last_affected":[],"package":"github.com/crypto-org-chain/cronos","purl":"pkg:golang/github.com/crypto-org-chain/cronos","source":"GHSA-gwj5-wp6r-5q9f"},{"ecosystem":"Go","fixed":["0.8.0"],"introduced":["0"],"last_affected":[],"package":"github.com/crypto-org-chain/cronos","purl":"pkg:golang/github.com/crypto-org-chain/cronos","source":"GO-2022-0829"}],"products":null,"published":"2022-08-11","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"An attacker can cause denial of service for smart contracts sharing identical bytecode by triggering a selfdestruct on one contract, affecting all instances.","url":"https://insights.sbomify.com/GHSA-gwj5-wp6r-5q9f/"}