CVE-2020-35915: Futures intrusive Data Races Vulnerability

MODERATE
Advisory Identifier: GHSA-4hjg-cx88-g9f9
Share
CVSS 5.5
CWE-362
Published
Advisory Summary

CVE-2020-35915 is a MODERATE (CVSS 5.5) data races vulnerability (CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')) affecting Futures intrusive libraries in the crates.io ecosystem. The issue involves data races in futures-intrusive. Remediation is available by upgrading affected packages to version 0.4.0.

CVE-2020-35915 at a Glance

CVE Identifier CVE-2020-35915
GHSA Identifier GHSA-4hjg-cx88-g9f9
Severity MODERATE
CVSS v3.1 Base Score 5.5
CWE Classification CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Affected Product Futures intrusive
Package Ecosystem crates.io
Published Date
Last Updated

Security Impact

CVSS: 5.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2020-35915

To remediate this vulnerability, upgrade all affected Futures intrusive dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

futures-intrusive fixed: 0.4.0 
Upgrade futures-intrusive to 0.4.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for futures-intrusive

How to Check if You Are Affected

To determine whether your application is affected by CVE-2020-35915, inspect your project dependencies for Futures intrusive:

inspect dependencies for futures-intrusive

Analyze the terminal output to locate any version of Futures intrusive in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.4.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'), where the product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently. In Futures intrusive, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

GenericMutexGuard<T> was given the Sync auto trait as long as T is Send due to its contained members. However, since the guard is supposed to represent an acquired lock and allows concurrent access to the underlying data from different threads, it should only be Sync when the underlying data is. This is a soundness issue and allows data races, potentially leading to crashes and segfaults from safe Rust code. The flaw was corrected by adding a T: Send + Sync bound for GenericMutexGuard's Sync trait.

CVE-2020-35915 Affected Futures intrusive Versions

1 component(s)
Fixed Versions:
0.4.0
Product / Package Ecosystem Affected Versions Fixed Version
futures-intrusive
 crates.io
< 0.4.0
0.4.0

References

NVD — CVE-2020-35915 NVD
https://nvd.nist.gov/vuln/detail/CVE-2020-35915
Futures intrusive Source Repository REPOSITORY
https://github.com/Matthias247/futures-intrusive/issues/53
Futures intrusive Source Repository REPOSITORY
https://github.com/Matthias247/futures-intrusive
rustsec.org/advisories/rustsec-... WEB
https://rustsec.org/advisories/RUSTSEC-2020-0072.html

Frequently Asked Questions

What is CVE-2020-35915?
CVE-2020-35915 is a security vulnerability in Futures intrusive involving Data races in futures-intrusive under CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition').
Which Futures intrusive versions are affected?
Affected versions include releases prior to 0.4.0 across affected packages: futures-intrusive.
What version fixes CVE-2020-35915?
Upgrading to 0.4.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is futures-intrusive affected?
Yes, futures-intrusive is affected in releases prior to 0.4.0. Upgrade your dependency to 0.4.0 or later.
What is the CVSS score of CVE-2020-35915?
CVE-2020-35915 has a CVSS v3.1 base score of 5.5 (MODERATE) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2020-35915?
CVE-2020-35915 is classified under CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') (The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.).
How can I check crates.io dependencies for CVE-2020-35915?
Run the dependency tree command: 'inspect dependencies for futures-intrusive'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-4hjg-cx88-g9f9",
  "modified" : "2023-06-13T18:10:45Z",
  "published" : "2021-08-25T20:49:58Z",
  "aliases" : [ "CVE-2020-35915" ],
  "summary" : "Data races in futures-intrusive",
  "details" : "GenericMutexGuard<T> was given the Sync auto trait as long as T is Send due to its contained members. However, since the guard is supposed to represent an acquired lock and allows concurrent access to the underlying data from different threads, it should only be Sync when the underlying data is.\n\nThis is a soundness issue and allows data races, potentially leading to crashes and segfaults from safe Rust code.\n\nThe flaw was corrected by adding a T: Send + Sync bound for GenericMutexGuard's Sync trait.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "futures-intrusive"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.4.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2020-35915"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/Matthias247/futures-intrusive/issues/53"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/Matthias247/futures-intrusive"
  }, {
    "type" : "WEB",
    "url" : "https://rustsec.org/advisories/RUSTSEC-2020-0072.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-362" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2021-08-19T20:49:04Z",
    "nvd_published_at" : null
  }
}