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

CVE-2020-36463

HIGH

CVE-2020-36463 is a high-severity (CVSS 8.1) CWE-77 vulnerability in multiqueue. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2020-36463 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Data races in multiqueue

Also known asGHSA-r2x6-vrxx-jgv4RUSTSEC-2020-0143
Published
Aug 25, 2021
Updated
Nov 8, 2023
Affected
1 pkg
Patched
None yet
Exploits
1 known
Exploitation data as of Nov 8, 2023 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🦀multiqueue

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

Affected versions of multiqueue unconditionally implemented Send for types used in queue implementations (InnerSend<RW, T>, InnerRecv<RW, T>, FutInnerSend<RW, T>, FutInnerRecv<RW, T>). This allows users to send non-Send types to other threads, which can lead to data race bugs or other undefined behavior.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
🦀crates.iomultiqueueall versionsNo fix
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 multiqueue. 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. Remediation status

    No patched version of multiqueue has shipped for CVE-2020-36463 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    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-36463 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-36463. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Affected versions of multiqueue unconditionally implemented `Send` for types used in queue implementations (`InnerSend<RW, T>`, `InnerRecv<RW, T>`, `FutInnerSend<RW, T>`, `FutInnerRecv<RW, T>`). This allows users to send non-Send types to other threads, which can lead to data race bugs or other undefined behavior.
O3 Security · Impact-Aware SCA

Is CVE-2020-36463 in your dependencies?

O3 detects CVE-2020-36463 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.

CVE-2020-36463: Data races in multiqueue… | O3 Security