rustsec-2020-0111
Vulnerability from osv_rustsec
Published
2020-11-10 12:00
Modified
2024-10-25 18:45
Summary
may_queue's Queue lacks Send/Sync bound for its Send/Sync trait.
Details
Affected versions of may_queue implements Send/Sync for its Queue type without restricting it to Sendable types and Syncable types.
This allows non-Sync types such as Cell to be shared across threads leading to undefined behavior and memory corruption in concurrent programs.
{
"affected": [
{
"database_specific": {
"categories": [
"memory-corruption",
"thread-safety"
],
"cvss": "CVSS:3.1/AV:N/AC:H/PR:N/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": "may_queue",
"purl": "pkg:cargo/may_queue"
},
"ranges": [
{
"events": [
{
"introduced": "0.0.0-0"
},
{
"fixed": "0.1.8"
}
],
"type": "SEMVER"
}
],
"versions": []
}
],
"aliases": [
"CVE-2020-36217",
"GHSA-pphf-f93w-gc84"
],
"database_specific": {
"license": "CC0-1.0"
},
"details": "Affected versions of `may_queue` implements `Send`/`Sync` for its `Queue` type without restricting it to `Send`able types and `Sync`able types.\n\nThis allows non-`Sync` types such as `Cell` to be shared across threads leading to undefined behavior and memory corruption in concurrent programs.",
"id": "RUSTSEC-2020-0111",
"modified": "2024-10-25T18:45:36Z",
"published": "2020-11-10T12:00:00Z",
"references": [
{
"type": "PACKAGE",
"url": "https://crates.io/crates/may_queue"
},
{
"type": "ADVISORY",
"url": "https://rustsec.org/advisories/RUSTSEC-2020-0111.html"
},
{
"type": "REPORT",
"url": "https://github.com/Xudong-Huang/may/issues/88"
}
],
"related": [],
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
],
"summary": "may_queue\u0027s Queue lacks Send/Sync bound for its Send/Sync trait."
}
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…