Attestkeep
Langue : Français
S'inscrire

Vulnérabilités / CVE-2024-32644

critique

CVE-2024-32644

Evmos transaction execution not accounting for all state transition after interaction with precompiles

Publiée Modifiée CWE 662
Dans la Trivy database depuis au moins le 24 oct. 2026, 07:11 UTCLa date d'entrée avant ce build n'est pas enregistrée.

Sévérité par source

NVD9.1CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
GHSA9.1CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Le label propre à Trivy est CRITICAL. Critique selon NVD, GHSA.

Description

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.

Paquets affectés et versions corrigées

SourcePaquetCorrigé en
go::GitHub Security Advisory Gogithub.com/evmos/evmos/v16, github.com/evmos/evmos/v5, github.com/evmos/evmos/v6 et 6 autres17.0.0
Afficher les 9 entrées d'une source
SourcePaquetCorrigé en
go::GitHub Security Advisory Gogithub.com/evmos/evmos/v1617.0.0
go::GitHub Security Advisory Gogithub.com/evmos/evmos/v5pas de correctif indiqué
go::GitHub Security Advisory Gogithub.com/evmos/evmos/v6pas de correctif indiqué
go::GitHub Security Advisory Gogithub.com/evmos/evmos/v7pas de correctif indiqué
go::GitHub Security Advisory Gogithub.com/tharsis/evmospas de correctif indiqué
go::GitHub Security Advisory Gogithub.com/tharsis/evmos/v2pas de correctif indiqué
go::GitHub Security Advisory Gogithub.com/tharsis/evmos/v3pas de correctif indiqué
go::GitHub Security Advisory Gogithub.com/tharsis/evmos/v4pas de correctif indiqué
go::GitHub Security Advisory Gogithub.com/tharsis/evmos/v5pas de correctif indiqué

Références

Vulnerability data compiled from the Trivy vulnerability database (trivy-db, Aqua Security, Apache License 2.0), which aggregates third-party advisories. CVE records are published by The MITRE Corporation under the CVE Terms of Use; CVE is a trademark of MITRE. This product uses data from the NVD API but is not endorsed or certified by the NVD. Severity, titles and advisory data from the GitHub Advisory Database (CC BY 4.0), Red Hat security data (CC BY 4.0) and the other sources linked on each entry. Entries may be summarised or re-formatted; the linked original is the authoritative record.