Most recent entries from all

cnvd-2022-04018

2026-10-12T17:52:30.199642+00:00

cnvd-2022-04018

EUVD-2026-33532

2026-10-12T17:52:30.199671+00:00

EUVD-2026-33532

fkie_cve-2021-45684

2026-10-12T17:52:30.199686+00:00

An issue was discovered in the flumedb crate through 2021-01-07 for Rust. read_entry may read from uninitialized memory locations.

GHSA-p46c-w9m3-7qr2 — Use of Uninitialized Resource in flumedb.

2026-10-12T17:52:30.199712+00:00

Affected: crates.io: flumedb

Affected versions of this crate passes an uninitialized buffer to a user-provided Read implementation. There are two of such cases (go_offset_log::read_entry() & offset_log::read_entry()).

Arbitrary Read implementations can read from the uninitialized buffer (memory exposure) and also can return incorrect number of bytes written to the buffer. Reading from uninitialized memory produces undefined values that can quickly invoke undefined behavior.

gsd-2021-45684

2026-10-12T17:52:30.199736+00:00

gsd-2021-45684

RUSTSEC-2021-0086 — `Read` on uninitialized buffer may cause UB ( `read_entry()` )

2026-10-12T17:52:30.199747+00:00

Affected: crates.io: flumedb

Affected versions of this crate passes an uninitialized buffer to a user-provided `Read` implementation. There are two of such cases (`go_offset_log::read_entry()` & `offset_log::read_entry()`).

Arbitrary `Read` implementations can read from the uninitialized buffer (memory exposure) and also can return incorrect number of bytes written to the buffer. Reading from uninitialized memory produces undefined values that can quickly invoke undefined behavior.