CosmWasm wasmd has large address count in ValidateBasicGHSA-m3rh-cvr5-x6q4
LOWFix: CosmWasm/wasmd@76c0c06GHSA-m3rh-cvr5-x6q4 is a low-severity (CVSS 3.7) vulnerability in github.com/CosmWasm/wasmd. A fix is available for github.com/CosmWasm/wasmd — see the affected versions and patch details below.
Real-World Exposure
github.com/CosmWasm/wasmdReal-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
Component: wasmd Criticality: Low (ACMv1: I:Moderate; L:Unlikely) Patched versions: wasmd 0.52.0
In multiple wasmd message types it was possible to add a large number of addresses which might lead to unexpected resource consumption in ValidateBasic.
See CWA-2024-003 for more details.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/CosmWasm/wasmd | all versions | 0.52.0go get github.com/CosmWasm/wasmd@v0.52.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/CosmWasm/wasmd, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/CosmWasm/wasmd to 0.52.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m3rh-cvr5-x6q4 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.
Frequently Asked Questions
Is GHSA-m3rh-cvr5-x6q4 in your dependencies?
Find it across Go, including transitive dependencies.