CVE-2020-36439: Ticketed lock Data Races Vulnerability

HIGH
Advisory Identifier: GHSA-77m6-x95j-75r5
Share
CVSS 8.1
CWE-362 CWE-119
Published
Advisory Summary

CVE-2020-36439 is a HIGH (CVSS 8.1) data races vulnerability (CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')) affecting Ticketed lock libraries in the crates.io ecosystem. The issue involves data races in ticketed_lock. Remediation is available by upgrading affected packages to version 0.3.0.

CVE-2020-36439 at a Glance

CVE Identifier CVE-2020-36439
GHSA Identifier GHSA-77m6-x95j-75r5
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 Ticketed lock
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 CVE-2020-36439

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

ticketed_lock fixed: 0.3.0 
Upgrade ticketed_lock to 0.3.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 ticketed_lock

How to Check if You Are Affected

To determine whether your application is affected by CVE-2020-36439, inspect your project dependencies for Ticketed lock:

inspect dependencies for ticketed_lock

Analyze the terminal output to locate any version of Ticketed lock in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.3.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 Ticketed lock, 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

Affected versions of this crate unconditionally implemented Send for ReadTicket<T> & WriteTicket<T>. This allows to send non-Send T to other threads. This can allows creating data races by cloning types with internal mutability and sending them to other threads (as T of ReadTicket<T>/WriteTicket<T>). Such data races can cause memory corruption or other undefined behavior. The flaw was corrected in commit `a986a93` by adding T: Send bounds to Send impls of ReadTicket<T>/WriteTicket<T>.

CVE-2020-36439 Affected Ticketed lock Versions

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

References

NVD — CVE-2020-36439 NVD
https://nvd.nist.gov/vuln/detail/CVE-2020-36439
Ticketed lock Source Repository REPOSITORY
https://github.com/kvark/ticketed_lock/issues/7
Security Fix Commit FIX COMMIT
https://github.com/kvark/ticketed_lock/commit/a986a9335d591fa5c826157d1674d47aa525357f
Ticketed lock Source Repository REPOSITORY
https://github.com/kvark/ticketed_lock
raw.githubusercontent.com/rustsec/advisory-db... WEB
https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/ticketed_lock/RUSTSEC-2020-0119.md
rustsec.org/advisories/rustsec-... WEB
https://rustsec.org/advisories/RUSTSEC-2020-0119.html

Frequently Asked Questions

What is CVE-2020-36439?
CVE-2020-36439 is a security vulnerability in Ticketed lock involving Data races in ticketed_lock under CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition').
Which Ticketed lock versions are affected?
Affected versions include releases prior to 0.3.0 across affected packages: ticketed_lock.
What version fixes CVE-2020-36439?
Upgrading to 0.3.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is ticketed_lock affected?
Yes, ticketed_lock is affected in releases prior to 0.3.0. Upgrade your dependency to 0.3.0 or later.
What is the CVSS score of CVE-2020-36439?
CVE-2020-36439 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 CVE-2020-36439?
CVE-2020-36439 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-36439?
Run the dependency tree command: 'inspect dependencies for ticketed_lock'. 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-77m6-x95j-75r5",
  "modified" : "2023-06-13T22:07:15Z",
  "published" : "2021-08-25T20:58:58Z",
  "aliases" : [ "CVE-2020-36439" ],
  "summary" : "Data races in ticketed_lock",
  "details" : "Affected versions of this crate unconditionally implemented Send for ReadTicket<T> & WriteTicket<T>. This allows to send non-Send T to other threads. This can allows creating data races by cloning types with internal mutability and sending them to other threads (as T of ReadTicket<T>/WriteTicket<T>). Such data races can cause memory corruption or other undefined behavior. The flaw was corrected in commit `a986a93` by adding T: Send bounds to Send impls of ReadTicket<T>/WriteTicket<T>.",
  "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" : "ticketed_lock"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.3.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2020-36439"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/kvark/ticketed_lock/issues/7"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/kvark/ticketed_lock/commit/a986a9335d591fa5c826157d1674d47aa525357f"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/kvark/ticketed_lock"
  }, {
    "type" : "WEB",
    "url" : "https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/ticketed_lock/RUSTSEC-2020-0119.md"
  }, {
    "type" : "WEB",
    "url" : "https://rustsec.org/advisories/RUSTSEC-2020-0119.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-119", "CWE-362" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2021-08-09T22:40:34Z",
    "nvd_published_at" : "2021-08-08T06:15:00Z"
  }
}