CVE-2020-35901: RUSTSEC-2020-0048 - Use-after-free in BodyStream due to lack of pinning

CVE-2020-35901 · Severity: low · CVSS 3.1 · Published 2020-01-24

Use-after-free in BodyStream due to lack of pinning

Technologies: actix-http (crates.io). Vendors: crates.io.

Quick answers

Is CVE-2020-35901 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2020-35901 being exploited in the wild.
How severe is CVE-2020-35901?
Low severity, with a CVSS score of 3.1, published 24 January 2020.
Which products and versions are affected?
actix-http (crates.io) SEMVER:introduced=0,fixed=2.0.0, SEMVER:introduced=0.0.0-0,fixed=2.0.0-alpha.1.
Is there a fix for CVE-2020-35901?
Yes. actix-http (crates.io): upgrade to 2.0.0, 2.0.0-alpha.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2020-35901?
Check whether you run actix-http (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.

How to fix

  • actix-http (crates.io): upgrade to 2.0.0, 2.0.0-alpha.1 or later
    cargo update -p actix-http

Affected products

  • actix-http (crates.io) SEMVER:introduced=0,fixed=2.0.0, SEMVER:introduced=0.0.0-0,fixed=2.0.0-alpha.1

Identifiers

  • CVE-2020-35901
  • GHSA-v3j6-xf77-8r9c
  • RUSTSEC-2020-0048

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