CVE-2020-35913: Lock api Data Races Vulnerability

MODERATE
Advisory Identifier: GHSA-hj9h-wrgg-hgmx
CVSS 4.7
CWE-362
Published
Advisory Summary

CVE-2020-35913 is a MODERATE (CVSS 4.7) data races vulnerability (CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')) affecting Lock api libraries in the crates.io ecosystem. The issue involves data races in lock_api. Remediation is available by upgrading affected packages to version 0.4.2.

CVE-2020-35913 at a Glance

CVE Identifier CVE-2020-35913
GHSA Identifier GHSA-hj9h-wrgg-hgmx
Severity MODERATE
CVSS v3.1 Base Score 4.7
CWE Classification CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Affected Product Lock api
Package Ecosystem crates.io
Published Date
Last Updated

Security Impact

CVSS: 4.7

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

Attack Vector Local (AV:L)
Attack Complexity High (AC:H)
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-35913

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

lock_api fixed: 0.4.2
Upgrade lock_api to 0.4.2
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 lock_api

How to Check if You Are Affected

To determine whether your application is affected by CVE-2020-35913, inspect your project dependencies for Lock api:

inspect dependencies for lock_api

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

An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of RwLockReadGuard unsoundness.

CVE-2020-35913 Affected Lock api Versions

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

References

Frequently Asked Questions

What is CVE-2020-35913?
CVE-2020-35913 is a security vulnerability in Lock api involving Data races in lock_api under CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition').
Which Lock api versions are affected?
Affected versions include releases prior to 0.4.2 across affected packages: lock_api.
What version fixes CVE-2020-35913?
Upgrading to 0.4.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is lock_api affected?
Yes, lock_api is affected in releases prior to 0.4.2. Upgrade your dependency to 0.4.2 or later.
What is the CVSS score of CVE-2020-35913?
CVE-2020-35913 has a CVSS v3.1 base score of 4.7 (MODERATE) with vector string CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2020-35913?
CVE-2020-35913 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-35913?
Run the dependency tree command: 'inspect dependencies for lock_api'. 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
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-hj9h-wrgg-hgmx",
  "modified" : "2021-08-19T18:59:37Z",
  "published" : "2021-08-25T20:50:02Z",
  "aliases" : [ "CVE-2020-35913" ],
  "summary" : "Data races in lock_api",
  "details" : "An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of RwLockReadGuard unsoundness.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "lock_api"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.4.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2020-35913"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/Amanieu/parking_lot/pull/262"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/Amanieu/parking_lot"
  }, {
    "type" : "WEB",
    "url" : "https://rustsec.org/advisories/RUSTSEC-2020-0070.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-362" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2021-08-19T18:59:37Z",
    "nvd_published_at" : null
  }
}