CVSS 3.1
5.3 mediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LMedium (5.3). EPSS 1.5% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/evmos/ethermint 0.18.0.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:Lgithub.com/evmos/ethermint (Go): fixed in 0.18.0github.com/evmos/evmos (Go): fixed in 7.0.0github.com/crypto-org-chain/cronos (Go): fixed in 0.7.1-rc2github.com/Kava-Labs/kava (Go): fixed in 0.18.0github.com/evmos/evmos/v7 (Go): fixed in 7.0.0github.com/kava-labs/kava (Go): fixed in 0.18.0Explain CVE-2022-35936 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-35936?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-35936?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2022-35936 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| evmos:ethermint | before 0.18.0 |
| kava:kava | before 0.18.0 |
| crypto:cronos | through 0.7.0 |
| evmos:evmos | before 7.0.0 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-f92v-grc2-w2fg | Go | github.com/evmos/ethermint | <0.18.0 | 0.18.0 |
| GHSA-f92v-grc2-w2fg | Go | github.com/evmos/evmos | <7.0.0 | 7.0.0 |
| GHSA-f92v-grc2-w2fg | Go | github.com/crypto-org-chain/cronos | <0.7.1-rc2 | 0.7.1-rc2 |
| GHSA-f92v-grc2-w2fg | Go | github.com/Kava-Labs/kava | <0.18.0 | 0.18.0 |
| GO-2022-0760 | Go | github.com/crypto-org-chain/cronos | <0.7.1-rc2 | 0.7.1-rc2 |
| GO-2022-0760 | Go | github.com/evmos/ethermint | <0.18.0 | 0.18.0 |
| GO-2022-0760 | Go | github.com/evmos/evmos | all versions | no fix published |
| GO-2022-0760 | Go | github.com/evmos/evmos/v2 | all versions | no fix published |
| GO-2022-0760 | Go | github.com/evmos/evmos/v3 | all versions | no fix published |
| GO-2022-0760 | Go | github.com/evmos/evmos/v4 | all versions | no fix published |
| GO-2022-0760 | Go | github.com/evmos/evmos/v5 | all versions | no fix published |
| GO-2022-0760 | Go | github.com/evmos/evmos/v6 | all versions | no fix published |
| GO-2022-0760 | Go | github.com/evmos/evmos/v7 | <7.0.0 | 7.0.0 |
| GO-2022-0760 | Go | github.com/kava-labs/kava | <0.18.0 | 0.18.0 |