What is GHSA-RG2Q-2JH9-447Q?

GHSA-RG2Q-2JH9-447Q is a medium-severity security vulnerability in cosmwasm-vm (rust), affecting versions < 1.5.6. It is fixed in 1.5.6, 2.0.5, 2.1.2, 2.0.3, 1.5.4.

How severe is GHSA-RG2Q-2JH9-447Q?

GHSA-RG2Q-2JH9-447Q has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which packages are affected by GHSA-RG2Q-2JH9-447Q?

cosmwasm-vm (rust) versions = 2.1.0, < 2.1.2; github.com/CosmWasm/wasmvm (go) versions < 1.5.4.

Is there a fix for GHSA-RG2Q-2JH9-447Q?

Yes. GHSA-RG2Q-2JH9-447Q is fixed in 1.5.6, 2.0.5, 2.1.2, 2.0.3, 1.5.4. Upgrade to this version or later.

Is GHSA-RG2Q-2JH9-447Q exploitable, and should I be worried?

Whether GHSA-RG2Q-2JH9-447Q 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-RG2Q-2JH9-447Q 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.

GHSA-RG2Q-2JH9-447Q in cosmwasm-vm

Q: How severe is GHSA-RG2Q-2JH9-447Q?

GHSA-RG2Q-2JH9-447Q has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which packages are affected by GHSA-RG2Q-2JH9-447Q?

cosmwasm-vm (rust) versions = 2.1.0, < 2.1.2; github.com/CosmWasm/wasmvm (go) versions < 1.5.4.

Q: Is there a fix for GHSA-RG2Q-2JH9-447Q?

Yes. GHSA-RG2Q-2JH9-447Q is fixed in 1.5.6, 2.0.5, 2.1.2, 2.0.3, 1.5.4. Upgrade to this version or later.

Q: Is GHSA-RG2Q-2JH9-447Q exploitable, and should I be worried?

Whether GHSA-RG2Q-2JH9-447Q 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-RG2Q-2JH9-447Q 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-RG2Q-2JH9-447Q?

Upgrade: cosmwasm-vm to 1.5.6 or later, cosmwasm-vm to 2.0.5 or later, cosmwasm-vm to 2.1.2 or later, github.com/CosmWasm/wasmvm/v2 to 2.1.2 or later, github.com/CosmWasm/wasmvm/v2 to 2.0.3 or later, github.com/CosmWasm/wasmvm to 1.5.4 or later.

Summary

Gas mispricing in cosmwasm-vm

Component: wasmvm
Criticality: Medium (ACMv1: I:Moderate; L:Likely)
Patched versions: wasmvm 1.5.4, 2.0.3, 2.1.2

Some Wasm operations take significantly more gas than our benchmarks indicated. This can lead to missing the gas target we defined by a factor of ~10x. This means a malicious contract could take 10 times as much time to execute as expected, which can be used to temporarily DoS a chain.

See CWA-2024-004 for more details.

Impact

GHSA-RG2Q-2JH9-447Q has a CVSS score of 4.3 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.5.6, 2.0.5, 2.1.2, 2.0.3, 1.5.4); upgrading removes the vulnerable code path.

Affected versions

cosmwasm-vm (< 1.5.6) cosmwasm-vm (>= 2.0.0, < 2.0.5) cosmwasm-vm (>= 2.1.0, < 2.1.2) github.com/CosmWasm/wasmvm/v2 (>= 2.1.0, < 2.1.2) github.com/CosmWasm/wasmvm/v2 (>= 2.0.0, < 2.0.3) github.com/CosmWasm/wasmvm (< 1.5.4)

Security releases

cosmwasm-vm → 1.5.6 (rust) cosmwasm-vm → 2.0.5 (rust) cosmwasm-vm → 2.1.2 (rust) github.com/CosmWasm/wasmvm/v2 → 2.1.2 (go) github.com/CosmWasm/wasmvm/v2 → 2.0.3 (go) github.com/CosmWasm/wasmvm → 1.5.4 (go)

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

Upgrade the following packages to resolve this vulnerability:

cosmwasm-vm to 1.5.6 or later; cosmwasm-vm to 2.0.5 or later; cosmwasm-vm to 2.1.2 or later; github.com/CosmWasm/wasmvm/v2 to 2.1.2 or later; github.com/CosmWasm/wasmvm/v2 to 2.0.3 or later; github.com/CosmWasm/wasmvm to 1.5.4 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-RG2Q-2JH9-447Q? GHSA-RG2Q-2JH9-447Q is a medium-severity security vulnerability in cosmwasm-vm (rust), affecting versions < 1.5.6. It is fixed in 1.5.6, 2.0.5, 2.1.2, 2.0.3, 1.5.4.
How severe is GHSA-RG2Q-2JH9-447Q? GHSA-RG2Q-2JH9-447Q has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which packages are affected by GHSA-RG2Q-2JH9-447Q?
- cosmwasm-vm (rust) (versions < 1.5.6)
- github.com/CosmWasm/wasmvm/v2 (go) (versions >= 2.1.0, < 2.1.2)
- github.com/CosmWasm/wasmvm (go) (versions < 1.5.4)
Is there a fix for GHSA-RG2Q-2JH9-447Q? Yes. GHSA-RG2Q-2JH9-447Q is fixed in 1.5.6, 2.0.5, 2.1.2, 2.0.3, 1.5.4. Upgrade to this version or later.
Is GHSA-RG2Q-2JH9-447Q exploitable, and should I be worried? Whether GHSA-RG2Q-2JH9-447Q 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-RG2Q-2JH9-447Q 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-RG2Q-2JH9-447Q?
- Upgrade cosmwasm-vm to 1.5.6 or later
- Upgrade cosmwasm-vm to 2.0.5 or later
- Upgrade cosmwasm-vm to 2.1.2 or later
- Upgrade github.com/CosmWasm/wasmvm/v2 to 2.1.2 or later
- Upgrade github.com/CosmWasm/wasmvm/v2 to 2.0.3 or later
- Upgrade github.com/CosmWasm/wasmvm to 1.5.4 or later

Other vulnerabilities in cosmwasm-vm

CVE-IDSeverityPackage summary

GHSA-MX2J-7CMV-353CMediumcosmwasm-vm: wasmvm: Malicious smart contract can slow down block production GHSA-2Q97-M5RC-P3GPMediumgithub.com/CosmWasm/wasmvm/v2: CosmWasm VM Incorrect metering GHSA-VMQH-5232-V43RMediumgithub.com/CosmWasm/wasmvm/v2: Panic in wasmvm can slow down block production GHSA-75QH-GG76-P2W4Mediumcosmwasm-vm: CWA-2023-004: Excessive number of function parameters in compiled Wasm