rustsec-2020-0134
Vulnerability from osv_rustsec
Published
2020-11-14 12:00
Modified
2023-06-13 13:10
Summary
`LockWeak<T>` allows to create data race to `T`.
Details
In the affected versions of this crate, LockWeak<T> unconditionally implemented Send with no trait bounds on T. LockWeak<T> doesn't own T and only provides &T.
This allows concurrent access to a non-Sync T, which can cause undefined behavior like data races.
{
"affected": [
{
"database_specific": {
"categories": [
"memory-corruption",
"thread-safety"
],
"cvss": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
"informational": null
},
"ecosystem_specific": {
"affected_functions": null,
"affects": {
"arch": [],
"functions": [],
"os": []
}
},
"package": {
"ecosystem": "crates.io",
"name": "parc",
"purl": "pkg:cargo/parc"
},
"ranges": [
{
"events": [
{
"introduced": "0.0.0-0"
}
],
"type": "SEMVER"
}
],
"versions": []
}
],
"aliases": [
"CVE-2020-36454",
"GHSA-29v7-3v4c-gf38",
"GHSA-xwxc-j97j-84gf"
],
"database_specific": {
"license": "CC0-1.0"
},
"details": "In the affected versions of this crate, `LockWeak\u003cT\u003e` unconditionally implemented `Send` with no trait bounds on `T`. `LockWeak\u003cT\u003e` doesn\u0027t own `T` and only provides `\u0026T`.\n\nThis allows concurrent access to a non-Sync `T`, which can cause undefined behavior like data races.",
"id": "RUSTSEC-2020-0134",
"modified": "2023-06-13T13:10:24Z",
"published": "2020-11-14T12:00:00Z",
"references": [
{
"type": "PACKAGE",
"url": "https://crates.io/crates/parc"
},
{
"type": "ADVISORY",
"url": "https://rustsec.org/advisories/RUSTSEC-2020-0134.html"
},
{
"type": "WEB",
"url": "https://github.com/hyyking/rustracts/pull/6"
}
],
"related": [],
"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": "`LockWeak\u003cT\u003e` allows to create data race to `T`."
}
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…