Approved changes feed: RSS · Atom
cpe:2.3:a:evmos:ethermint:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Evmos (28c11bd4-c3b2-5c7c-be58-341bc13d8617) |
|---|---|
| Product | Ethermint (481d4073-5fe5-5e4e-aeb6-94948da2e4a1) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/evmos/ethermint |
purl2cpe | 2026-06-01 10:17:30.195559 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2022-35936 |
vulnerable | 2026-06-08 05:46:06.016842 |
Ethermint DoS through Unintended Contract Selfdestruct
HIGH (8.2)
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.
Published: 2022-08-05T12:55:11.000Z
Updated: 2025-04-22T17:42:50.952Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.