LowGO-2024-3101GHSA-75qh-gg76-p2w4RUSTSEC-2024-0366

Excessive number of function parameters in compiled Wasm in github.com/CosmWasm/wasmvm

Published 20 Dec 2024 · Updated 3 Mar 2026

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 package

Affected
<1.2.5 · >=1.3.0 <1.3.1 · >=1.4.0 <1.4.2 · >=1.5.0 <1.5.1
Fixed in
1.2.5, 1.3.1, 1.4.2, 1.5.1
Update to the fixed version for your release line, for example:go get github.com/CosmWasm/wasmvm@v1.5.1

Details

A specifically crafted Wasm file can cause the VM to consume excessive amounts of memory when compiling a contract. This can lead to high memory usage, slowdowns, potentially a crash and can poison a lock in the VM, preventing any further interaction with contracts.

Is GO-2024-3101 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
  • LowGO-2025-3449wasmvm: Malicious smart contract can slow down block production in github.com/CosmWasm/wasmvm · 5 Feb 2025
  • MediumGHSA-mx2j-7cmv-353cwasmvm: Malicious smart contract can slow down block production · 4 Feb 2025
  • MediumGHSA-23qp-3c2m-xx6wwasmvm: Malicious smart contract can crash the chain · 4 Feb 2025
  • MediumGHSA-2q97-m5rc-p3gpCosmWasm VM Incorrect metering · 10 Dec 2024
  • MediumGHSA-vmqh-5232-v43rPanic in wasmvm can slow down block production · 10 Dec 2024
All 8 advisories for github.com/CosmWasm/wasmvm

References

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