GHSA-mm4m-qg48-f7wc
HIGHGHSA-mm4m-qg48-f7wc is a high-severity (CVSS 7.5) CWE-362 vulnerability in vm-memory. O3 Security confirms whether GHSA-mm4m-qg48-f7wc is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Improper Synchronization and Race Condition in vm-memory
Real-World Exposure
vm-memory🦀vm-memoryReal-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
rust-vmm vm-memory before 0.1.1 and 0.2.x before 0.2.1 allows attackers to cause a denial of service (loss of IP networking) because read_obj and write_obj do not properly access memory. This affects aarch64 (with musl or glibc) and x86_64 (with musl).
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | vm-memory | all versions | 0.1.1 |
| 🦀crates.io | vm-memory | ≥ 0.2.0&&< 0.2.1 | 0.2.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vm-memory. 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 vm-memory to 0.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mm4m-qg48-f7wc 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-mm4m-qg48-f7wc 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-mm4m-qg48-f7wc. 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-mm4m-qg48-f7wc in your dependencies?
O3 detects GHSA-mm4m-qg48-f7wc 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.