CVE-2020-36465
HIGHCVE-2020-36465 is a high-severity (CVSS 7.5) vulnerability in generic-array. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2020-36465 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Use after free in generic-array
Real-World Exposure
generic-array🦀generic-array🦀generic-array🦀generic-array🦀generic-arrayReal-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
An issue was discovered in the generic-array crate before 0.13.3 for Rust. It violates soundness by using the arr! macro to extend lifetimes.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | generic-array | ≥ 0.13.0&&< 0.13.3 | 0.13.3 |
| 🦀crates.io | generic-array | ≥ 0.12.0&&< 0.12.4 | 0.12.4 |
| 🦀crates.io | generic-array | ≥ 0.11.0&&< 0.11.2 | 0.11.2 |
| 🦀crates.io | generic-array | ≥ 0.10.0&&< 0.10.1 | 0.10.1 |
| 🦀crates.io | generic-array | ≥ 0.8.0&&< 0.9.1 | 0.9.1 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for generic-array. 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 generic-array to 0.13.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-36465 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 CVE-2020-36465 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 CVE-2020-36465. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2020-36465 in your dependencies?
O3 detects CVE-2020-36465 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.