MediumGHSA-mx2j-7cmv-353cGO-2025-3449

wasmvm: Malicious smart contract can slow down block production

Published 4 Feb 2025 · Updated 9 Jul 2025

Is your project on an affected github.com/CosmWasm/wasmvm?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=0.1.0 <1.5.8
Fixed in
1.5.8
Update to the fixed version for your release line, for example:go get github.com/CosmWasm/wasmvm@v1.5.8
Affected
>=2.2.0 <2.2.2
Fixed in
2.2.2
Update to the fixed version for your release line, for example:go get github.com/CosmWasm/wasmvm/v2@v2.2.2
Affected
>=2.1.0 <2.1.5
Fixed in
2.1.5
Update to the fixed version for your release line, for example:go get github.com/CosmWasm/wasmvm/v2@v2.1.5
Affected
>=2.0.0 <2.0.6
Fixed in
2.0.6
Update to the fixed version for your release line, for example:go get github.com/CosmWasm/wasmvm/v2@v2.0.6
Affected
<0.0.0-20250204093451-1f4db20199b8
Fixed in
0.0.0-20250204093451-1f4db20199b8
Update to the fixed version for your release line, for example:go get github.com/CosmWasm/wasmvm@v0.0.0-20250204093451-1f4db20199b8
Affected
<2.0.0-20250204103256-d62c3b826a9d
Fixed in
2.0.0-20250204103256-d62c3b826a9d
Update to the fixed version for your release line, for example:go get github.com/CosmWasm/wasmvm/v2@v2.0.0-20250204103256-d62c3b826a9d
Affected
>=1.5.8-0 <1.5.8-0.20250204093451-1f4db20199b8
Fixed in
1.5.8-0.20250204093451-1f4db20199b8
Update to the fixed version for your release line, for example:go get github.com/CosmWasm/wasmvm@v1.5.8-0.20250204093451-1f4db20199b8
Affected
>=2.0.6-0 <2.0.6-0.20250204103256-d62c3b826a9d
Fixed in
2.0.6-0.20250204103256-d62c3b826a9d
Update to the fixed version for your release line, for example:go get github.com/CosmWasm/wasmvm/v2@v2.0.6-0.20250204103256-d62c3b826a9d

Details

CWA-2025-002

Severity

Medium (Moderate + Likely)[^1]

Affected versions:

  • wasmvm >= 2.2.0, < 2.2.2
  • wasmvm >= 2.1.0, < 2.1.5
  • wasmvm >= 2.0.0, < 2.0.6
  • wasmvm < 1.5.8

Patched versions:

  • wasmvm 1.5.8, 2.0.6, 2.1.5, 2.2.2

Description of the bug

The vulnerability can be used to slow down block production. The attack requires a malicious contract, so permissioned chains are unlikely to be affected.

(We'll add more detail once chains had a chance to upgrade.)

Patch

  • 1.5: https://github.com/CosmWasm/cosmwasm/commit/2b7f2faa57a1efc8207455c37f87f1eee6035a27
  • 2.0: https://github.com/CosmWasm/cosmwasm/commit/d6143b0aff16a39bbea4be37597d8e9d9b213d3b
  • 2.1: https://github.com/CosmWasm/cosmwasm/commit/f0c04c03cbe2557634c1bbcdc2ce203fe7caca58
  • 2.2: https://github.com/CosmWasm/cosmwasm/commit/a5d62f65b5eb947ebe40e2085b1c48a9d0a244d0

Applying the patch

The patch will be shipped in releases of wasmvm. You can update more or less as follows:

1. Check the current wasmvm version: go list -m github.com/CosmWasm/wasmvm 2. Bump the github.com/CosmWasm/wasmvm dependency in your go.mod to one of the patched version depending on which minor version you are on; go mod tidy; commit. 3. If you use the static libraries libwasmvm_muslc.aarch64.a/libwasmvm_muslc.x86_64.a, update them accordingly. 4. Check the updated wasmvm version: go list -m github.com/CosmWasm/wasmvm and ensure you see 1.5.8, 2.0.6, 2.1.5 or 2.2.2. 5. Follow your regular practices to deploy chain upgrades.

The patch is consensus breaking and requires a coordinated upgrade.

Acknowledgement

This issue was found by meadow101 who reported it to the Cosmos Bug Bounty Program on HackerOne.

If you believe you have found a bug in the Interchain Stack or would like to contribute to the program by reporting a bug, please see <https://hackerone.com/cosmos>.

Timeline

  • 2024-11-24: Confio receives a report through the Cosmos bug bounty program maintained by Amulet.
  • 2024-12-20: Confio security contributors confirm the report.
  • 2024-01-27: Confio developed the patch internally.
  • 2025-02-04: Patch gets released.

[^1]: following Amulet's Severity Classification Framework ACMv1.2: https://github.com/interchainio/security/blob/0295254e8645301ccb606d46108a45cede0a73e0/resources/CLASSIFICATION_MATRIX.md

Is GHSA-mx2j-7cmv-353c in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/CosmWasm/wasmvm, and gives you the command that fixes it.

More advisories for github.com/CosmWasm/wasmvm

  • LowGO-2025-3448Malicious smart contract can crash the chain in github.com/CosmWasm/wasmvm · 5 Feb 2025
  • MediumGHSA-23qp-3c2m-xx6wwasmvm: Malicious smart contract can crash the chain · 4 Feb 2025
  • LowGO-2024-3101Excessive number of function parameters in compiled Wasm in github.com/CosmWasm/wasmvm · 20 Dec 2024
  • MediumGHSA-2q97-m5rc-p3gpCosmWasm VM Incorrect metering · 10 Dec 2024
  • MediumGHSA-vmqh-5232-v43rPanic in wasmvm can slow down block production · 10 Dec 2024
  • MediumGHSA-75qh-gg76-p2w4CWA-2023-004: Excessive number of function parameters in compiled Wasm · 27 Aug 2024
All 8 advisories for github.com/CosmWasm/wasmvm

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.