Most recent entries from all

cnvd-2022-04516

2026-10-19T21:00:56.045322+00:00

cnvd-2022-04516

EUVD-2026-33530

2026-10-19T21:00:56.045356+00:00

EUVD-2026-33530

fkie_cve-2021-45704

2026-10-19T21:00:56.045370+00:00

An issue was discovered in the metrics-util crate before 0.7.0 for Rust. There is a data race and memory corruption because AtomicBucket unconditionally implements the Send and Sync traits.

GHSA-cwvc-87xq-pc5m — Out-of-bounds Write and Race Condition in metrics-util

2026-10-19T21:00:56.045398+00:00

Affected: crates.io: metrics-util

In the affected versions of the crate, AtomicBucket 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 (which is a data type contained inside AtomicBucket).

gsd-2021-45704

2026-10-19T21:00:56.045424+00:00

gsd-2021-45704

RUSTSEC-2021-0113 — AtomicBucket unconditionally implements Send/Sync

2026-10-19T21:00:56.045436+00:00

Affected: crates.io: metrics-util

In the affected versions of the crate, `AtomicBucket` 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` (which is a data type contained inside `AtomicBucket`).