GHSA-3HXH-7JXM-59X4
Vulnerability from github – Published: 2022-06-17 00:13 – Updated: 2022-06-17 00:13
VLAI?
Summary
AtomicBucket<T> unconditionally implements Send/Sync
Details
In the affected versions of the crate, AtomicBucket<T> unconditionally implements Send/Sync traits. Therefore, users can create a data race to the inner
T: !Sync by using the AtomicBucket::data_with() API.
Such data races can potentially cause memory corruption or other undefined behavior.
The flaw was fixed in commit 8e6daab by adding appropriate Send/Sync bounds to the Send/Sync impl of struct Block<T> (which is a data type contained inside AtomicBucket<T>).
{
"affected": [
{
"package": {
"ecosystem": "crates.io",
"name": "metrics-util"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.7.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [],
"database_specific": {
"cwe_ids": [],
"github_reviewed": true,
"github_reviewed_at": "2022-06-17T00:13:03Z",
"nvd_published_at": null,
"severity": "MODERATE"
},
"details": "In the affected versions of the crate, `AtomicBucket\u003cT\u003e` unconditionally implements `Send`/`Sync` traits. Therefore, users can create a data race to the inner\n`T: !Sync` by using the `AtomicBucket::data_with()` API.\nSuch data races can potentially cause memory corruption or other undefined behavior.\n\nThe flaw was fixed in commit 8e6daab by adding appropriate Send/Sync bounds to the Send/Sync impl of struct `Block\u003cT\u003e` (which is a data type contained inside `AtomicBucket\u003cT\u003e`).\n",
"id": "GHSA-3hxh-7jxm-59x4",
"modified": "2022-06-17T00:13:03Z",
"published": "2022-06-17T00:13:03Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/metrics-rs/metrics/issues/190"
},
{
"type": "PACKAGE",
"url": "https://github.com/metrics-rs/metrics"
},
{
"type": "WEB",
"url": "https://rustsec.org/advisories/RUSTSEC-2021-0113.html"
}
],
"schema_version": "1.4.0",
"severity": [],
"summary": "AtomicBucket\u003cT\u003e unconditionally implements Send/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…