GHSA-g8w7-7vgg-x7xg
HIGHCWA-2024-005: Stackoverflow in wasmd
Blast Radius
github.com/CosmWasm/wasmd🐹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: High (ACMv1: I:Critical; L:Likely) Patched versions: wasmd 0.53.0, 0.46.0
See CWA-2024-005 for more details.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/CosmWasm/wasmd | ≥ 0.50.0&&< 0.53.0 | 0.53.0 |
| 🐹Go | github.com/CosmWasm/wasmd | all versions | 0.46.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. 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.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g8w7-7vgg-x7xg 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-g8w7-7vgg-x7xg 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-g8w7-7vgg-x7xg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-g8w7-7vgg-x7xg in your dependencies?
O3 detects GHSA-g8w7-7vgg-x7xg across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.