How severe is GHSA-2q97-m5rc-p3gp?

No CVSS score has been assigned to GHSA-2q97-m5rc-p3gp yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2q97-m5rc-p3gp?

GHSA-2q97-m5rc-p3gp affects the following packages: cosmwasm-vm (crates.io), cosmwasm-vm (crates.io), cosmwasm-vm (crates.io), github.com/CosmWasm/wasmvm/v2 (Go), github.com/CosmWasm/wasmvm/v2 (Go), github.com/CosmWasm/wasmvm (Go). Ecosystems affected: crates.io, Go.

How do I fix GHSA-2q97-m5rc-p3gp?

Update cosmwasm-vm to 2.1.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2q97-m5rc-p3gp is resolved across your whole dependency graph.

How do I detect GHSA-2q97-m5rc-p3gp in my crates.io, Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for cosmwasm-vm. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-2q97-m5rc-p3gp if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-2q97-m5rc-p3gp?

O3 pinpoints whether GHSA-2q97-m5rc-p3gp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-2q97-m5rc-p3gp actively exploited in the wild?

No public exploit code has been indexed for GHSA-2q97-m5rc-p3gp yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-2q97-m5rc-p3gp published, and has it been updated?

GHSA-2q97-m5rc-p3gp was published on December 10, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-2q97-m5rc-p3gp: CosmWasm VM Incorrect metering

Blast Radius

6 pkgs affected

🦀cosmwasm-vm🦀cosmwasm-vm🦀cosmwasm-vm🐹github.com/CosmWasm/wasmvm/v2🐹github.com/CosmWasm/wasmvm/v2🐹github.com/CosmWasm/wasmvm

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

CWA-2024-007

Severity

Medium (Moderate + Likely)¹

Affected versions:

wasmvm >= 2.1.0, < 2.1.3
wasmvm >= 2.0.0, < 2.0.4
wasmvm < 1.5.5
cosmwasm-vm >= 2.1.0, < 2.1.4
cosmwasm-vm >= 2.0.0, < 2.0.7
cosmwasm-vm < 1.5.8

Patched versions:

wasmvm 1.5.5, 2.0.4, 2.1.3
cosmwasm-vm 1.5.8, 2.0.7, 2.1.4

Description of the bug

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

Patch

Applying the patch

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

Check the current wasmvm version: go list -m github.com/CosmWasm/wasmvm
Bump the github.com/CosmWasm/wasmvm dependency in your go.mod to 1.5.5, 2.0.4, 2.1.3 depending on which minor version you are; go mod tidy; commit.
If you use the static libraries libwasmvm_muslc.aarch64.a/libwasmvm_muslc.x86_64.a, update them accordingly.
Check the updated wasmvm version: go list -m github.com/CosmWasm/wasmvm and ensure you see 1.5.5, 2.0.4, 2.1.3.
Follow your regular practices to deploy chain upgrades.

To double check if the correct library version is loaded at runtime, use this query: <appd> query wasm libwasmvm-version. It must show 1.5.5, 2.0.4 or 2.1.3.

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-08-28: Confio receives a report through the Cosmos bug bounty program maintained by Amulet.
2024-08-30: Confio security contributors confirm the report.
2024-09-02: Confio developed the patch internally.
2024-09-23: Patch is released.

Footnotes

following Amulet's Severity Classification Framework ACMv1: https://github.com/interchainio/security/blob/e0227a1fb4059144aab4f6003eeee7f09912db3a/resources/CLASSIFICATION_MATRIX.md ↩

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`cosmwasm-vm`	≥ 2.1.0&&< 2.1.4	2.1.4
🦀crates.io	`cosmwasm-vm`	≥ 2.0.0&&< 2.0.7	2.0.7
🦀crates.io	`cosmwasm-vm`	all versions	1.5.8
🐹Go	`github.com/CosmWasm/wasmvm/v2`	≥ 2.1.0&&< 2.1.3	2.1.3
🐹Go	`github.com/CosmWasm/wasmvm/v2`	≥ 2.0.0&&< 2.0.4	2.0.4
🐹Go	`github.com/CosmWasm/wasmvm`	all versions	1.5.5

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for cosmwasm-vm. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update cosmwasm-vm to 2.1.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2q97-m5rc-p3gp is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-2q97-m5rc-p3gp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-2q97-m5rc-p3gp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

# CWA-2024-007 **Severity** Medium (Moderate + Likely)[^1] **Affected versions:** - wasmvm >= 2.1.0, < 2.1.3 - wasmvm >= 2.0.0, < 2.0.4 - wasmvm < 1.5.5 - cosmwasm-vm >= 2.1.0, < 2.1.4 - cosmwasm-vm >= 2.0.0, < 2.0.7 - cosmwasm-vm < 1.5.8 **Patched versions:** - wasmvm 1.5.5, 2.0.4, 2.1.3 - cosmwasm-vm 1.5.8, 2.0.7, 2.1.4 ## Description of the bug (Blank for now. We'll add more detail once chains had a chance to upgrade.) ## Patch - 1.5: https://github.com/CosmWasm/cosmwasm/commit/16eabd681790508b13dac8e67f9e6e61045240ea - 2.0: https://github.com/CosmWasm/cosmwasm/commit/0e70bd83119b

O3 Security · Impact-Aware SCA

Is GHSA-2q97-m5rc-p3gp in your dependencies?

O3 detects GHSA-2q97-m5rc-p3gp across crates.io, Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-2q97-m5rc-p3gp