CVE-2020-35900: RUSTSEC-2020-0047 - array_queue pop_back() may cause a use-after-free

CVE-2020-35900 · Severity: low · CVSS 3.1 · Published 2020-09-26

array_queue pop_back() may cause a use-after-free

Technologies: array-queue (crates.io). Vendors: crates.io.

Quick answers

Is CVE-2020-35900 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2020-35900 being exploited in the wild.
How severe is CVE-2020-35900?
Low severity, with a CVSS score of 3.1, published 26 September 2020.
Which products and versions are affected?
array-queue (crates.io) SEMVER:introduced=0.3.0, SEMVER:introduced=0.3.0,last_affected=0.3.3.
Is there a fix for CVE-2020-35900?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
Am I affected by CVE-2020-35900?
Check whether you run array-queue (crates.io) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Affected products

  • array-queue (crates.io) SEMVER:introduced=0.3.0, SEMVER:introduced=0.3.0,last_affected=0.3.3

Identifiers

  • CVE-2020-35900
  • GHSA-75cq-g75g-rxff
  • RUSTSEC-2020-0047

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.