rustsec-2021-0036
Vulnerability from osv_rustsec
Published
2021-03-03 12:00
Modified
2023-06-13 13:10
Summary
Intern<T>: Data race allowed on T
Details
Affected versions of this crate unconditionally implements Sync for Intern<T>.
This allows users to create data race on T: !Sync, which may lead to undefined behavior
(for example, memory corruption).
The flaw was corrected in commit 2928a87 by adding the trait bound T: Sync in the Sync impl of Intern<T>.
{
"affected": [
{
"database_specific": {
"categories": [
"thread-safety"
],
"cvss": "CVSS:3.1/AV:N/AC:L/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": "internment",
"purl": "pkg:cargo/internment"
},
"ranges": [
{
"events": [
{
"introduced": "0.0.0-0"
},
{
"fixed": "0.4.2"
}
],
"type": "SEMVER"
}
],
"versions": []
}
],
"aliases": [
"CVE-2021-28037",
"GHSA-gppw-3h6h-v6q2"
],
"database_specific": {
"license": "CC0-1.0"
},
"details": "Affected versions of this crate unconditionally implements `Sync` for `Intern\u003cT\u003e`.\nThis allows users to create data race on `T: !Sync`, which may lead to undefined behavior\n(for example, memory corruption).\n\nThe flaw was corrected in commit 2928a87 by adding the trait bound `T: Sync` in the `Sync` impl of `Intern\u003cT\u003e`.",
"id": "RUSTSEC-2021-0036",
"modified": "2023-06-13T13:10:24Z",
"published": "2021-03-03T12:00:00Z",
"references": [
{
"type": "PACKAGE",
"url": "https://crates.io/crates/internment"
},
{
"type": "ADVISORY",
"url": "https://rustsec.org/advisories/RUSTSEC-2021-0036.html"
},
{
"type": "REPORT",
"url": "https://github.com/droundy/internment/issues/20"
}
],
"related": [],
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "Intern\u003cT\u003e: Data race allowed on 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…