rustsec-2020-0118
Vulnerability from osv_rustsec
Published
2020-12-08 12:00
Modified
2023-06-13 13:10
Summary
Future<T> lacks bounds on Send and Sync.
Details
tiny_future contains a light-weight implementation of Futures. The Future
type it has lacked bound on its Send and Sync traits.
This allows for a bug where non-thread safe types such as Cell can be used in
Futures and cause data races in concurrent programs.
The flaw was corrected in commit c791919 by adding trait bounds to Future's
Send and Sync.
{
"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": "tiny_future",
"purl": "pkg:cargo/tiny_future"
},
"ranges": [
{
"events": [
{
"introduced": "0.0.0-0"
},
{
"fixed": "0.4.0"
}
],
"type": "SEMVER"
}
],
"versions": []
}
],
"aliases": [
"CVE-2020-36438",
"GHSA-fg42-vwxx-xx5j",
"GHSA-m296-j53x-xv95"
],
"database_specific": {
"license": "CC0-1.0"
},
"details": "`tiny_future` contains a light-weight implementation of `Future`s. The `Future`\ntype it has lacked bound on its `Send` and `Sync` traits.\n\nThis allows for a bug where non-thread safe types such as `Cell` can be used in\n`Future`s and cause data races in concurrent programs.\n\nThe flaw was corrected in commit `c791919` by adding trait bounds to `Future`\u0027s\n`Send` and `Sync`.",
"id": "RUSTSEC-2020-0118",
"modified": "2023-06-13T13:10:24Z",
"published": "2020-12-08T12:00:00Z",
"references": [
{
"type": "PACKAGE",
"url": "https://crates.io/crates/tiny_future"
},
{
"type": "ADVISORY",
"url": "https://rustsec.org/advisories/RUSTSEC-2020-0118.html"
},
{
"type": "REPORT",
"url": "https://github.com/KizzyCode/tiny_future/issues/1"
}
],
"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": "Future\u003cT\u003e lacks bounds on Send and Sync."
}
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…