GHSA-PFJQ-935C-4895
Vulnerability from github – Published: 2021-08-25 21:00 – Updated: 2023-06-13 22:27
VLAI?
Summary
Data races in v9
Details
Affected versions of this crate unconditionally implement Sync for SyncRef<T>. This definition allows data races if &T is accessible through &SyncRef.
SyncRef<T> derives Clone and Debug, and the default implementations of those traits access &T by invoking T::clone() & T::fmt(). It is possible to create data races & undefined behavior by concurrently invoking SyncRef<T>::clone() or SyncRef<T>::fmt() from multiple threads with T: !Sync.
Severity ?
8.1 (High)
{
"affected": [
{
"package": {
"ecosystem": "crates.io",
"name": "v9"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.1.43"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [],
"database_specific": {
"cwe_ids": [
"CWE-362"
],
"github_reviewed": true,
"github_reviewed_at": "2021-08-05T21:37:57Z",
"nvd_published_at": null,
"severity": "HIGH"
},
"details": "Affected versions of this crate unconditionally implement `Sync` for `SyncRef\u003cT\u003e`. This definition allows data races if `\u0026T` is accessible through `\u0026SyncRef`.\n\n`SyncRef\u003cT\u003e` derives `Clone` and `Debug`, and the default implementations of those traits access `\u0026T` by invoking `T::clone()` \u0026 `T::fmt()`. It is possible to create data races \u0026 undefined behavior by concurrently invoking `SyncRef\u003cT\u003e::clone()` or `SyncRef\u003cT\u003e::fmt()` from multiple threads with `T: !Sync`.\n",
"id": "GHSA-pfjq-935c-4895",
"modified": "2023-06-13T22:27:40Z",
"published": "2021-08-25T21:00:37Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/purpleposeidon/v9/issues/1"
},
{
"type": "WEB",
"url": "https://rustsec.org/advisories/RUSTSEC-2020-0127.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "Data races in v9"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…