GHSA-g4v2-cjqp-rfmq
HIGHCritical Use-After-Free in Wasmi's Linear Memory
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
wasmi🦀wasmi🦀wasmi🦀wasmiReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.
Description
Summary
A use-after-free vulnerability has been discovered in the linear memory implementation of Wasmi. This issue can be triggered by a WebAssembly module under certain memory growth conditions, potentially leading to memory corruption, information disclosure, or code execution.
Impact
- Confidentiality: High – attacker-controlled memory reads possible.
- Integrity: High – memory corruption may allow arbitrary writes.
- Availability: High – interpreter crashes possible.
Affected Versions
Wasmi v0.41.0 through Wasmi v1.0.0.
Workarounds
- Upgrade to the latest patched version of Wasmi.
- Consider limiting the maximum linear memory sizes where feasible.
Credits
This vulnerability was discovered by Robert T. Morris (RTM).
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | wasmi | ≥ 0.41.0&&< 0.41.2 | 0.41.2 |
| 🦀crates.io | wasmi | ≥ 0.42.0&&< 0.47.1 | 0.47.1 |
| 🦀crates.io | wasmi | ≥ 0.50.0&&< 0.51.3 | 0.51.3 |
| 🦀crates.io | wasmi | ≥ 1.0.0&&< 1.0.1 | 1.0.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for wasmi. 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 wasmi to 0.41.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g4v2-cjqp-rfmq 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-g4v2-cjqp-rfmq 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-g4v2-cjqp-rfmq. 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-g4v2-cjqp-rfmq in your dependencies?
O3 detects GHSA-g4v2-cjqp-rfmq across crates.io dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.