How severe is GHSA-vmg2-r3xv-r3xf?

No CVSS score has been assigned to GHSA-vmg2-r3xv-r3xf yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-vmg2-r3xv-r3xf?

GHSA-vmg2-r3xv-r3xf affects the following packages: github.com/CosmWasm/wasmd (Go). Ecosystems affected: Go.

How do I fix GHSA-vmg2-r3xv-r3xf?

Update github.com/CosmWasm/wasmd to 0.53.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vmg2-r3xv-r3xf is resolved across your whole dependency graph.

How do I detect GHSA-vmg2-r3xv-r3xf in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/CosmWasm/wasmd. 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-vmg2-r3xv-r3xf 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-vmg2-r3xv-r3xf?

O3 pinpoints whether GHSA-vmg2-r3xv-r3xf 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-vmg2-r3xv-r3xf actively exploited in the wild?

No public exploit code has been indexed for GHSA-vmg2-r3xv-r3xf 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-vmg2-r3xv-r3xf published, and has it been updated?

GHSA-vmg2-r3xv-r3xf was published on December 10, 2024 and was last updated 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.

🐹 Go

GHSA-vmg2-r3xv-r3xf

Simulation of Wasmd message can cause crashing

Also known asGO-2024-3319

Published

Dec 10, 2024

Updated

Dec 10, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🐹github.com/CosmWasm/wasmd

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

Description

CWA-2024-009

Severity

Low (Marginal + Likely)¹

Affected versions:

wasmd < 0.53.1

Patched versions:

wasmd 0.53.2 (please note that wasmd 0.53.1 is broken and must not be used)

Description of the bug

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

Mitigations

Apart from upgrading, it is recommended to not open the gRPC and REST APIs of validator nodes to the public internet. Use isolated and resource-constrained environments for running separate public RPC nodes instead. These can then easily be thrown away and replaced with new instances in case of problems.

Applying the patch

Official Wasmd patch

The patch will be shipped in a wasmd release. You will also have to update libwasmvm if you build statically. If you already use the latest / close to latest wasmd, you can update more or less as follows:

Check the current wasmd version: go list -m github.com/CosmWasm/wasmd
Bump the github.com/CosmWasm/wasmd dependency in your go.mod to 0.53.2 (Cosmos SDK 0.50 compatible); go mod tidy; commit.
If you use the static libraries libwasmvm_muslc.aarch64.a/libwasmvm_muslc.x86_64.a, make sure that you use the same version as your wasmvm version.
Check the updated wasmd version: go list -m github.com/CosmWasm/wasmd and ensure you see 0.53.2.
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 2.1.4.

The patch is not consensus breaking if you are already using wasmvm 2.1.3. If you are instead using wasmvm 2.1.2, then upgrading to 2.1.4 includes the consensus breaking changes of 2.1.3.

DIY Patch

If you are unable to upgrade to the latest version, you can backport the wasmd patch to your version. The patch is available at Wasmd 0.53.2. However, if you are on an older version of wasmd, you will also be using a different version of wasmvm. We provide the required patches for wasmvm in versions 2.1.4, 2.0.5, 1.5.6. To upgrade using this method:

Check the current wasmvm version: go list -m github.com/CosmWasm/wasmvm and upgrade to the closest patched version.
Bump the github.com/CosmWasm/wasmvm dependency in your go.mod to the closest compatible patched version (either 2.1.4, 2.0.5 or 1.5.6); go mod tidy; commit.
Apply the patch linked above to your version of wasmd.
If you use the static libraries libwasmvm_muslc.aarch64.a/libwasmvm_muslc.x86_64.a, make sure that you use the same version as your wasmvm version.
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 2.1.4, 2.0.5 or 1.5.6 and must be the same as the wasmvm version in your go.sum.

The patch is not consensus breaking as long as you were using the previous patch version of wasmvm before.

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-09-25: Confio receives a report through the Cosmos bug bounty program maintained by Amulet.
2024-09-30: Confio security contributors confirm the report.
2024-11-21: Confio developed the patch internally.
2024-12-06: Patch release is pre-announced through notification lists.
2024-12-10: Patch released.

Footnotes

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

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/CosmWasm/wasmd`	all versions	0.53.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/CosmWasm/wasmd. 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 github.com/CosmWasm/wasmd to 0.53.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vmg2-r3xv-r3xf 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-vmg2-r3xv-r3xf 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-vmg2-r3xv-r3xf. 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-009 **Severity** Low (Marginal + Likely)[^1] **Affected versions:** - wasmd < 0.53.1 **Patched versions:** - wasmd 0.53.2 (please note that wasmd 0.53.1 is broken and must not be used) ## Description of the bug (Blank for now. We'll add more detail once chains had a chance to upgrade.) ## Mitigations Apart from upgrading, it is recommended to **not** open the gRPC and REST APIs of _validator_ nodes to the public internet. Use isolated and resource-constrained environments for running separate public RPC nodes instead. These can then easily be thrown away and replaced with

O3 Security · Impact-Aware SCA

Is GHSA-vmg2-r3xv-r3xf in your dependencies?

O3 detects GHSA-vmg2-r3xv-r3xf across 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