Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🦀 crates.io

CVE-2020-36465

HIGH

Use after free in generic-array

Also known asGHSA-3358-4f7f-p4j4RUSTSEC-2020-0146
Published
Aug 8, 2021
Updated
Apr 10, 2026
Affected
5 pkgs
Patched
5 / 5
Exploits
1 known

EPSS Exploitation Probability

via FIRST.org ↗
1.2%probability of exploitation in next 30 days
Lower Risk65th percentile+0.95%
0.00%0.58%1.16%1.73%0.3%1.2%Dec 25Apr 26Jun 26

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

5 pkgs affected
🦀generic-array🦀generic-array🦀generic-array🦀generic-array🦀generic-array

Real-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

5 total 5 fixed
EcosystemPackageVulnerable rangeFix
🦀crates.iogeneric-array0.13.0&&< 0.13.30.13.3
🦀crates.iogeneric-array0.12.0&&< 0.12.40.12.4
🦀crates.iogeneric-array0.11.0&&< 0.11.20.11.2
🦀crates.iogeneric-array0.10.0&&< 0.10.10.10.1
🦀crates.iogeneric-array0.8.0&&< 0.9.10.9.1
Exploits & PoCs
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 dependency
  1. Detect

    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.

  2. 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.

  3. 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.

  4. 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

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.
O3 Security · Impact-Aware SCA

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.