CVE-2020-36447 : An issue was discovered in the v9 crate through 2020-12-18 for Rust. There is an

An issue was discovered in the v9 crate through 2020-12-18 for Rust. There is an unconditional implementation of Sync for SyncRef<T>.

Published 2021-08-08 06:15:07

Updated 2022-11-03 02:50:30

Source MITRE

View at NVD, CVE.org

Products affected by CVE-2020-36447

V9 Project » V9 » For Rust
Versions up to, including, (<=) 0.1.41
cpe:2.3:a:v9_project:v9:*:*:*:*:*:rust:*:*
Matching versions

EPSS FAQ

0.62%

Probability of exploitation activity in the next 30 days EPSS Score History

~ 80 %

Percentile, the proportion of vulnerabilities that are scored at or less

Base Score	Base Severity	CVSS Vector	Exploitability Score	Impact Score	Score Source
6.8	MEDIUM	AV:N/AC:M/Au:N/C:P/I:P/A:P	8.6	6.4	NIST
Access Vector: Network Access Complexity: Medium Authentication: None Confidentiality Impact: Partial Integrity Impact: Partial Availability Impact: Partial
8.1	HIGH	CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H	2.2	5.9	NIST
Attack Vector: Network Attack Complexity: High Privileges Required: None User Interaction: None Scope: Unchanged Confidentiality: High Integrity: High Availability: High

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.

Assigned by: nvd@nist.gov (Primary)

https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/v9/RUSTSEC-2020-0127.md

Third Party Advisory
https://rustsec.org/advisories/RUSTSEC-2020-0127.html

RUSTSEC-2020-0127: v9: SyncRef's clone() and debug() allow data races › RustSec Advisory Database
Exploit;Third Party Advisory

Jump to