No. Junglewise Threat Intelligence has no report of CVE-2022-35936 being exploited in the wild.
How severe is CVE-2022-35936?
Low severity, with a CVSS score of 3.1, published 21 August 2024.
Which products and versions are affected?
github.com/crypto-org-chain/cronos (Go) SEMVER:introduced=0,fixed=0.7.1-rc2; github.com/evmos/ethermint (Go) SEMVER:introduced=0,fixed=0.18.0; github.com/evmos/evmos (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=7.0.0; github.com/evmos/evmos/v2 (Go) SEMVER:introduced=0; and 6 more.
Is there a fix for CVE-2022-35936?
Yes. github.com/crypto-org-chain/cronos (Go): upgrade to 0.7.1-rc2 or later; github.com/evmos/ethermint (Go): upgrade to 0.18.0 or later; github.com/evmos/evmos (Go): upgrade to 7.0.0 or later; github.com/evmos/evmos/v7 (Go): upgrade to 7.0.0 or later; github.com/Kava-Labs/kava (Go): upgrade to 0.18.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2022-35936?
Check whether you run github.com/crypto-org-chain/cronos (Go), github.com/evmos/ethermint (Go), github.com/evmos/evmos (Go) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
github.com/crypto-org-chain/cronos (Go): upgrade to 0.7.1-rc2 or later
go get github.com/crypto-org-chain/cronos@v0.7.1-rc2
github.com/evmos/ethermint (Go): upgrade to 0.18.0 or later
go get github.com/evmos/ethermint@v0.18.0
github.com/evmos/evmos (Go): upgrade to 7.0.0 or later
go get github.com/evmos/evmos@v7.0.0
github.com/evmos/evmos/v7 (Go): upgrade to 7.0.0 or later
go get github.com/evmos/evmos/v7@v7.0.0
github.com/Kava-Labs/kava (Go): upgrade to 0.18.0 or later