GHSA-gwj5-wp6r-5q9f: Github.com/crypto org chain/cronos Denial of Service Vulnerability
HIGHGHSA-gwj5-wp6r-5q9f is a HIGH (CVSS 8.2) denial of service vulnerability (CWE-668: Exposure of Resource to Wrong Sphere) affecting Github.com/crypto org chain/cronos libraries in the Go ecosystem. The issue involves cronos vulnerable to dos through unintended contract selfdestruct. Remediation is available by upgrading affected packages to version 0.8.0.
GHSA-gwj5-wp6r-5q9f at a Glance
Security Impact
CVSS: 8.2
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H).
How to Fix GHSA-gwj5-wp6r-5q9f
To remediate this vulnerability, upgrade all affected Github.com/crypto org chain/cronos dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade github.com/crypto-org-chain/cronos to 0.8.0
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for github.com/crypto-org-chain/cronos
How to Check if You Are Affected
To determine whether your application is affected by GHSA-gwj5-wp6r-5q9f, inspect your project dependencies for Github.com/crypto org chain/cronos:
inspect dependencies for github.com/crypto-org-chain/cronos
Analyze the terminal output to locate any version of Github.com/crypto org chain/cronos in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.8.0), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-668: Exposure of Resource to Wrong Sphere, where the product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource. In Github.com/crypto org chain/cronos, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
GHSA-gwj5-wp6r-5q9f Affected Github.com/crypto org chain/cronos Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
github.com/crypto-org-chain/cronos
|
Go |
< 0.8.0
|
0.8.0
|
References
Frequently Asked Questions
What is GHSA-gwj5-wp6r-5q9f?
Which Github.com/crypto org chain/cronos versions are affected?
What version fixes GHSA-gwj5-wp6r-5q9f?
Is github.com/crypto-org-chain/cronos affected?
What is the CVSS score of GHSA-gwj5-wp6r-5q9f?
What CWE is associated with GHSA-gwj5-wp6r-5q9f?
How can I check Go dependencies for GHSA-gwj5-wp6r-5q9f?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-gwj5-wp6r-5q9f",
"modified" : "2022-08-11T18:08:57Z",
"published" : "2022-08-11T18:08:57Z",
"aliases" : [ ],
"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.\n",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/crypto-org-chain/cronos"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "0.8.0"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 0.7.0"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/crypto-org-chain/cronos/security/advisories/GHSA-gwj5-wp6r-5q9f"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2022-35936"
}, {
"type" : "WEB",
"url" : "https://github.com/crypto-org-chain/cronos/commit/2f2cc88b501b47149690fdef05afbbbe5bc116c9"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/crypto-org-chain/cronos"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-668" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2022-08-11T18:08:57Z",
"nvd_published_at" : null
}
}