CVE-2020-36207: Aovec Data Races Vulnerability

HIGH
Advisory Identifier: GHSA-g489-xrw3-3v8w
CVSS 7.0
CWE-662 CWE-787
Published
Advisory Summary

CVE-2020-36207 is a HIGH (CVSS 7.0) data races vulnerability (CWE-662: Improper Synchronization) affecting Aovec libraries in the crates.io ecosystem. The issue involves data races in aovec. Remediation is available in the latest vendor maintenance releases.

CVE-2020-36207 at a Glance

CVE Identifier CVE-2020-36207
GHSA Identifier GHSA-g489-xrw3-3v8w
Severity HIGH
CVSS v3.1 Base Score 7.0
CWE Classification CWE-662: Improper Synchronization
Affected Product Aovec
Package Ecosystem crates.io
Published Date
Last Updated

Security Impact

CVSS: 7.0

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:H/I:H/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 High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2020-36207

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

aovec fixed: Latest secure release
Upgrade aovec to Latest secure release
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 aovec

How to Check if You Are Affected

To determine whether your application is affected by CVE-2020-36207, inspect your project dependencies for Aovec:

inspect dependencies for aovec

Analyze the terminal output to locate any version of Aovec in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), 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-662: Improper Synchronization, where the product utilizes multiple threads, processes, components, or systems to allow temporary access to a shared resource that can only be exclusive to one process at a time, but it does not properly synchronize these actions, which might cause simultaneous accesses of this resource by multiple threads or processes. In Aovec, 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 aovec crate through 2020-12-10 for Rust. Because Aovec<T> does not have bounds on its Send trait or Sync trait, a data race and memory corruption can occur.

CVE-2020-36207 Affected Aovec Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
aovec
crates.io
≤ 1.1.0

References

Frequently Asked Questions

What is CVE-2020-36207?
CVE-2020-36207 is a security vulnerability in Aovec involving Data races in aovec under CWE-662: Improper Synchronization.
Which Aovec versions are affected?
Affected versions include releases prior to current release patches across affected packages: aovec.
What version fixes CVE-2020-36207?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is aovec affected?
Yes, aovec is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of CVE-2020-36207?
CVE-2020-36207 has a CVSS v3.1 base score of 7.0 (HIGH) with vector string CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2020-36207?
CVE-2020-36207 is classified under CWE-662: Improper Synchronization (The product utilizes multiple threads, processes, components, or systems to allow temporary access to a shared resource that can only be exclusive to one process at a time, but it does not properly synchronize these actions, which might cause simultaneous accesses of this resource by multiple threads or processes.).
How can I check crates.io dependencies for CVE-2020-36207?
Run the dependency tree command: 'inspect dependencies for aovec'. 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-g489-xrw3-3v8w",
  "modified" : "2021-08-19T18:51:25Z",
  "published" : "2021-08-25T20:50:46Z",
  "aliases" : [ "CVE-2020-36207" ],
  "summary" : "Data races in aovec",
  "details" : "An issue was discovered in the aovec crate through 2020-12-10 for Rust. Because Aovec<T> does not have bounds on its Send trait or Sync trait, a data race and memory corruption can occur.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "aovec"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "1.1.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2020-36207"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/krl/aovec"
  }, {
    "type" : "WEB",
    "url" : "https://rustsec.org/advisories/RUSTSEC-2020-0099.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-662", "CWE-787" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2021-08-19T18:51:25Z",
    "nvd_published_at" : null
  }
}