mirror of
https://github.com/OMGeeky/advisory-db.git
synced 2026-02-23 15:38:27 +01:00
Add disappeared advisories (#1049)
This commit is contained in:
18
crates/metrics-util/RUSTSEC-0000-0000.md
Normal file
18
crates/metrics-util/RUSTSEC-0000-0000.md
Normal file
@@ -0,0 +1,18 @@
|
||||
```toml
|
||||
[advisory]
|
||||
id = "RUSTSEC-0000-0000"
|
||||
package = "metrics-util"
|
||||
date = "2021-04-07"
|
||||
url = "https://github.com/metrics-rs/metrics/issues/190"
|
||||
categories = ["memory-corruption", "thread-safety"]
|
||||
[versions]
|
||||
patched = [">= 0.7.0"]
|
||||
```
|
||||
|
||||
# AtomicBucket<T> unconditionally implements Send/Sync
|
||||
|
||||
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>`).
|
||||
Reference in New Issue
Block a user