GHSA-m296-j53x-xv95: Tiny future Data Races Vulnerability

HIGH
Share
CVSS 8.1
CWE-362
Published
Advisory Summary

GHSA-m296-j53x-xv95 is a HIGH (CVSS 8.1) data races vulnerability (CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')) affecting Tiny future libraries in the crates.io ecosystem. The issue involves data races in tiny_future. Remediation is available by upgrading affected packages to version 0.4.0.

GHSA-m296-j53x-xv95 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-m296-j53x-xv95
Severity HIGH
CVSS v3.1 Base Score 8.1
CWE Classification CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Affected Product Tiny future
Package Ecosystem crates.io
Published Date
Last Updated

Security Impact

CVSS: 8.1

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

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

How to Fix GHSA-m296-j53x-xv95

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

tiny_future fixed: 0.4.0 
Upgrade tiny_future 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 tiny_future

How to Check if You Are Affected

To determine whether your application is affected by GHSA-m296-j53x-xv95, inspect your project dependencies for Tiny future:

inspect dependencies for tiny_future

Analyze the terminal output to locate any version of Tiny future 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 Tiny future, 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

`tiny_future` contains a light-weight implementation of `Future`s. The `Future` type it has lacked bound on its `Send` and `Sync` traits. This allows for a bug where non-thread safe types such as `Cell` can be used in `Future`s and cause data races in concurrent programs. The flaw was corrected in commit `c791919` by adding trait bounds to `Future`'s `Send` and `Sync`.

GHSA-m296-j53x-xv95 Affected Tiny future Versions

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

References

Tiny future Source Repository REPOSITORY
https://github.com/KizzyCode/tiny_future/issues/1
Security Fix Commit FIX COMMIT
https://github.com/KizzyCode/tiny_future/commit/7ab8a264980d23c2ed64e72f4636f38b7381eb39
Security Fix Commit FIX COMMIT
https://github.com/KizzyCode/tiny_future/commit/c7919199a0f6d1ce0e3c33499d1b37f862c990e4
Tiny future Source Repository REPOSITORY
https://github.com/KizzyCode/tiny_future
rustsec.org/advisories/rustsec-... WEB
https://rustsec.org/advisories/RUSTSEC-2020-0118.html

Frequently Asked Questions

What is GHSA-m296-j53x-xv95?
GHSA-m296-j53x-xv95 is a security vulnerability in Tiny future involving Data races in tiny_future under CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition').
Which Tiny future versions are affected?
Affected versions include releases prior to 0.4.0 across affected packages: tiny_future.
What version fixes GHSA-m296-j53x-xv95?
Upgrading to 0.4.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is tiny_future affected?
Yes, tiny_future is affected in releases prior to 0.4.0. Upgrade your dependency to 0.4.0 or later.
What is the CVSS score of GHSA-m296-j53x-xv95?
GHSA-m296-j53x-xv95 has a CVSS v3.1 base score of 8.1 (HIGH) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with GHSA-m296-j53x-xv95?
GHSA-m296-j53x-xv95 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 GHSA-m296-j53x-xv95?
Run the dependency tree command: 'inspect dependencies for tiny_future'. 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-m296-j53x-xv95",
  "modified" : "2023-06-13T21:47:59Z",
  "published" : "2021-08-25T21:00:32Z",
  "aliases" : [ ],
  "summary" : "Data races in tiny_future",
  "details" : "`tiny_future` contains a light-weight implementation of `Future`s. The `Future` type it has lacked bound on its `Send` and `Sync` traits. This allows for a bug where non-thread safe types such as `Cell` can be used in `Future`s and cause data races in concurrent programs. The flaw was corrected in commit `c791919` by adding trait bounds to `Future`'s `Send` and `Sync`.\n",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "tiny_future"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.4.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/KizzyCode/tiny_future/issues/1"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/KizzyCode/tiny_future/commit/7ab8a264980d23c2ed64e72f4636f38b7381eb39"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/KizzyCode/tiny_future/commit/c7919199a0f6d1ce0e3c33499d1b37f862c990e4"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/KizzyCode/tiny_future"
  }, {
    "type" : "WEB",
    "url" : "https://rustsec.org/advisories/RUSTSEC-2020-0118.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-362" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2021-08-05T22:01:31Z",
    "nvd_published_at" : null
  }
}