rustsec-2020-0087
Vulnerability from osv_rustsec
Published
2020-11-17 12:00
Modified
2023-06-13 13:10
Summary
TryMutex<T> allows sending non-Send type across threads
Details
Affected versions of this crate unconditionally implemented Sync trait for TryMutex<T> type.
This allows users to put non-Send T type in TryMutex and send it to another thread, which can cause a data race.
The flaw was corrected in the 0.3.0 release by adding T: Send bound for the Sync trait implementation.
{
"affected": [
{
"database_specific": {
"categories": [
"thread-safety"
],
"cvss": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
"informational": null
},
"ecosystem_specific": {
"affected_functions": null,
"affects": {
"arch": [],
"functions": [],
"os": []
}
},
"package": {
"ecosystem": "crates.io",
"name": "try-mutex",
"purl": "pkg:cargo/try-mutex"
},
"ranges": [
{
"events": [
{
"introduced": "0.0.0-0"
},
{
"fixed": "0.3.0"
}
],
"type": "SEMVER"
}
],
"versions": []
}
],
"aliases": [
"CVE-2020-35924",
"GHSA-64j8-7gp2-xjx5"
],
"database_specific": {
"license": "CC0-1.0"
},
"details": "Affected versions of this crate unconditionally implemented Sync trait for `TryMutex\u003cT\u003e` type.\n\nThis allows users to put non-Send `T` type in `TryMutex` and send it to another thread, which can cause a data race.\n\nThe flaw was corrected in the 0.3.0 release by adding `T: Send` bound for the Sync trait implementation.",
"id": "RUSTSEC-2020-0087",
"modified": "2023-06-13T13:10:24Z",
"published": "2020-11-17T12:00:00Z",
"references": [
{
"type": "PACKAGE",
"url": "https://crates.io/crates/try-mutex"
},
{
"type": "ADVISORY",
"url": "https://rustsec.org/advisories/RUSTSEC-2020-0087.html"
},
{
"type": "REPORT",
"url": "https://github.com/mpdn/try-mutex/issues/2"
}
],
"related": [],
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
],
"summary": "TryMutex\u003cT\u003e allows sending non-Send type across threads"
}
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…