Approved changes feed: RSS · Atom
cpe:2.3:a:evmos:evmos:-:*:*:*:*:*:*:*
part: a version: - update: *
| Vendor | Evmos (28c11bd4-c3b2-5c7c-be58-341bc13d8617) |
|---|---|
| Product | Evmos (3696918c-3213-58a1-a54e-f911bf968f81) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/evmos/evmos |
purl2cpe | 2026-06-01 10:17:30.162461 |
pkg:github/liyong828/evmos |
purl2cpe | 2026-06-01 10:17:30.162462 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-37154 |
vulnerable | 2026-06-08 06:39:46.724027 |
Evmos allows unvested token delegations
MEDIUM (5.3)
Evmos is the Ethereum Virtual Machine (EVM) Hub on the Cosmos Network. Users are able to delegate tokens that have not yet been vested. This affects employees and grantees who have funds managed via `ClawbackVestingAccount`. This affects 18.1.0 and earlier.
Published: 2024-06-06T19:04:08.386Z
Updated: 2024-08-02T03:50:55.197Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-32644 |
vulnerable | 2026-06-08 06:37:23.493391 |
Evmos' transaction execution not accounting for all state transition after interaction with precompiles
CRITICAL (9.1)
Evmos is a scalable, high-throughput Proof-of-Stake EVM blockchain that is fully compatible and interoperable with Ethereum. Prior to 17.0.0, there is a way to mint arbitrary tokens due to the possibility to have two different states not in sync during the execution of a transaction. The exploit is based on the fact that to sync the Cosmos SDK state and the EVM one, we rely on the `stateDB.Commit()` method. When we call this method, we iterate though all the `dirtyStorage` and, **if and only if** it is different than the `originStorage`, we set the new state. Setting the new state means we update the Cosmos SDK KVStore. If a contract storage state that is the same before and after a transaction, but is changed during the transaction and can call an external contract after the change, it can be exploited to make the transaction similar to non-atomic. The vulnerability is **critical** since this could lead to drain of funds through creative SC interactions. The issue has been patched in versions >=V17.0.0.
Published: 2024-04-19T14:53:44.423Z
Updated: 2024-08-02T02:13:40.251Z |
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.