What is GHSA-2Q97-M5RC-P3GP?

GHSA-2Q97-M5RC-P3GP is a medium-severity security vulnerability in github.com/CosmWasm/wasmvm/v2 (go), affecting versions >= 2.1.0, < 2.1.3. It is fixed in 2.1.3, 2.0.4, 1.5.5, 2.1.4, 2.0.7, 1.5.8.

Which packages are affected by GHSA-2Q97-M5RC-P3GP?

github.com/CosmWasm/wasmvm/v2 (go) versions >= 2.1.0, = 2.1.0, < 2.1.4.

Is there a fix for GHSA-2Q97-M5RC-P3GP?

Yes. GHSA-2Q97-M5RC-P3GP is fixed in 2.1.3, 2.0.4, 1.5.5, 2.1.4, 2.0.7, 1.5.8. Upgrade to this version or later.

Is GHSA-2Q97-M5RC-P3GP exploitable, and should I be worried?

Whether GHSA-2Q97-M5RC-P3GP is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-2Q97-M5RC-P3GP is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix GHSA-2Q97-M5RC-P3GP?

Upgrade: github.com/CosmWasm/wasmvm/v2 to 2.1.3 or later, github.com/CosmWasm/wasmvm/v2 to 2.0.4 or later, github.com/CosmWasm/wasmvm to 1.5.5 or later, cosmwasm-vm to 2.1.4 or later, cosmwasm-vm to 2.0.7 or later, cosmwasm-vm to 1.5.8 or later.

GHSA-2Q97-M5RC-P3GP in github.com/CosmWasm/wasmvm/v2

Q: Which packages are affected by GHSA-2Q97-M5RC-P3GP?

github.com/CosmWasm/wasmvm/v2 (go) versions >= 2.1.0, = 2.1.0, < 2.1.4.

Q: Is there a fix for GHSA-2Q97-M5RC-P3GP?

Yes. GHSA-2Q97-M5RC-P3GP is fixed in 2.1.3, 2.0.4, 1.5.5, 2.1.4, 2.0.7, 1.5.8. Upgrade to this version or later.

Q: Is GHSA-2Q97-M5RC-P3GP exploitable, and should I be worried?

Whether GHSA-2Q97-M5RC-P3GP is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-2Q97-M5RC-P3GP is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-2Q97-M5RC-P3GP?

Upgrade: github.com/CosmWasm/wasmvm/v2 to 2.1.3 or later, github.com/CosmWasm/wasmvm/v2 to 2.0.4 or later, github.com/CosmWasm/wasmvm to 1.5.5 or later, cosmwasm-vm to 2.1.4 or later, cosmwasm-vm to 2.0.7 or later, cosmwasm-vm to 1.5.8 or later.

Summary

CosmWasm VM Incorrect metering

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.)

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.

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

Impact

Affected versions

github.com/CosmWasm/wasmvm/v2 (>= 2.1.0, < 2.1.3) github.com/CosmWasm/wasmvm/v2 (>= 2.0.0, < 2.0.4) github.com/CosmWasm/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)

Security releases

github.com/CosmWasm/wasmvm/v2 → 2.1.3 (go) github.com/CosmWasm/wasmvm/v2 → 2.0.4 (go) github.com/CosmWasm/wasmvm → 1.5.5 (go) cosmwasm-vm → 2.1.4 (rust) cosmwasm-vm → 2.0.7 (rust) cosmwasm-vm → 1.5.8 (rust)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Frequently Asked Questions

What is GHSA-2Q97-M5RC-P3GP? GHSA-2Q97-M5RC-P3GP is a medium-severity security vulnerability in github.com/CosmWasm/wasmvm/v2 (go), affecting versions >= 2.1.0, < 2.1.3. It is fixed in 2.1.3, 2.0.4, 1.5.5, 2.1.4, 2.0.7, 1.5.8.
Which packages are affected by GHSA-2Q97-M5RC-P3GP?
- github.com/CosmWasm/wasmvm/v2 (go) (versions >= 2.1.0, < 2.1.3)
- github.com/CosmWasm/wasmvm (go) (versions < 1.5.5)
- cosmwasm-vm (rust) (versions >= 2.1.0, < 2.1.4)
Is there a fix for GHSA-2Q97-M5RC-P3GP? Yes. GHSA-2Q97-M5RC-P3GP is fixed in 2.1.3, 2.0.4, 1.5.5, 2.1.4, 2.0.7, 1.5.8. Upgrade to this version or later.
Is GHSA-2Q97-M5RC-P3GP exploitable, and should I be worried? Whether GHSA-2Q97-M5RC-P3GP is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-2Q97-M5RC-P3GP is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-2Q97-M5RC-P3GP?
- Upgrade github.com/CosmWasm/wasmvm/v2 to 2.1.3 or later
- Upgrade github.com/CosmWasm/wasmvm/v2 to 2.0.4 or later
- Upgrade github.com/CosmWasm/wasmvm to 1.5.5 or later
- Upgrade cosmwasm-vm to 2.1.4 or later
- Upgrade cosmwasm-vm to 2.0.7 or later
- Upgrade cosmwasm-vm to 1.5.8 or later

Other vulnerabilities in github.com/CosmWasm/wasmvm/v2

CVE-IDSeverityPackage summary

GHSA-MX2J-7CMV-353CMediumcosmwasm-vm: wasmvm: Malicious smart contract can slow down block production GHSA-23QP-3C2M-XX6WMediumgithub.com/CosmWasm/wasmvm: wasmvm: Malicious smart contract can crash the chain GHSA-VMQH-5232-V43RMediumgithub.com/CosmWasm/wasmvm/v2: Panic in wasmvm can slow down block production GHSA-RG2Q-2JH9-447QMediumcosmwasm-vm: Gas mispricing in cosmwasm-vm