CVE-2020-36220: Va ts Data Race Vulnerability
MODERATECVE-2020-36220 is a MODERATE (CVSS 5.9) data race vulnerability (CWE-662: Improper Synchronization) affecting Va ts libraries in the crates.io ecosystem. The issue involves data race in va-ts. Remediation is available by upgrading affected packages to version 0.0.4.
CVE-2020-36220 at a Glance
Security Impact
CVSS: 5.9
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:N/I:N/A:H).
How to Fix CVE-2020-36220
To remediate this vulnerability, upgrade all affected Va ts dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade va-ts to 0.0.4
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for va-ts
How to Check if You Are Affected
To determine whether your application is affected by CVE-2020-36220, inspect your project dependencies for Va ts:
inspect dependencies for va-ts
Analyze the terminal output to locate any version of Va ts in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.0.4), 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 Va ts, 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
CVE-2020-36220 Affected Va ts Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
va-ts
|
crates.io |
< 0.0.4
|
0.0.4
|
References
Frequently Asked Questions
What is CVE-2020-36220?
Which Va ts versions are affected?
What version fixes CVE-2020-36220?
Is va-ts affected?
What is the CVSS score of CVE-2020-36220?
What CWE is associated with CVE-2020-36220?
How can I check crates.io dependencies for CVE-2020-36220?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-3hj2-hh36-hv9v",
"modified" : "2023-06-13T22:11:43Z",
"published" : "2021-08-25T20:51:56Z",
"aliases" : [ "CVE-2020-36220" ],
"summary" : "Data race in va-ts",
"details" : "In the affected versions of this crate, Demuxer<T> unconditionally implemented Send with no trait bounds on T. This allows sending a non-Send type T across thread boundaries, which can cause undefined behavior like unlocking a mutex from a thread that didn't lock the mutex, or memory corruption from data race. The flaw was corrected in commit `0562cbf` by adding a T: Send bound to the Send impl for Demuxer<T>.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "crates.io",
"name" : "va-ts"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "0.0.4"
} ]
} ]
} ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2020-36220"
}, {
"type" : "WEB",
"url" : "https://github.com/video-audio/va-ts/issues/4"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/video-audio/va-ts"
}, {
"type" : "WEB",
"url" : "https://rustsec.org/advisories/RUSTSEC-2020-0114.html"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-662", "CWE-667", "CWE-787" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2021-08-19T18:47:06Z",
"nvd_published_at" : null
}
}