cve.bz

CVE-2022-35936 Exposure of Resource to Wrong Sphere

5.3 mediumExploit referenceEPSS 1.5%Fix available

Medium (5.3). EPSS 1.5% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/evmos/ethermint 0.18.0.

On this page
Ethermint is an Ethereum library. In Ethermint running versions before `v0.17.2`, the contract `selfdestruct` invocation permanently removes the corresponding bytecode from the internal database storage. However, due to a bug in the `DeleteAccount`function, 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. This vulnerability has been patched in Ethermint version v0.18.0. The patch has state machine-breaking changes for applications using Ethermint, so a coordinated upgrade procedure is required. A workaround is available. 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. The new contract deployment restores the `bytecode hash -> bytecode` entry in the internal state.

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS
1.5% (unchanged from 1.5% a week ago; 1.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 74th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2025-04-22. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-668 Exposure of Resource to Wrong Sphere
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain 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.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
evmos:ethermintbefore 0.18.0
kava:kavabefore 0.18.0
crypto:cronosthrough 0.7.0
evmos:evmosbefore 7.0.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-f92v-grc2-w2fgGogithub.com/evmos/ethermint<0.18.00.18.0
GHSA-f92v-grc2-w2fgGogithub.com/evmos/evmos<7.0.07.0.0
GHSA-f92v-grc2-w2fgGogithub.com/crypto-org-chain/cronos<0.7.1-rc20.7.1-rc2
GHSA-f92v-grc2-w2fgGogithub.com/Kava-Labs/kava<0.18.00.18.0
GO-2022-0760Gogithub.com/crypto-org-chain/cronos<0.7.1-rc20.7.1-rc2
GO-2022-0760Gogithub.com/evmos/ethermint<0.18.00.18.0
GO-2022-0760Gogithub.com/evmos/evmosall versionsno fix published
GO-2022-0760Gogithub.com/evmos/evmos/v2all versionsno fix published
GO-2022-0760Gogithub.com/evmos/evmos/v3all versionsno fix published
GO-2022-0760Gogithub.com/evmos/evmos/v4all versionsno fix published
GO-2022-0760Gogithub.com/evmos/evmos/v5all versionsno fix published
GO-2022-0760Gogithub.com/evmos/evmos/v6all versionsno fix published
GO-2022-0760Gogithub.com/evmos/evmos/v7<7.0.07.0.0
GO-2022-0760Gogithub.com/kava-labs/kava<0.18.00.18.0

References

Check your stackJSON