Most recent entries from all

cnvd-2021-17268

2026-10-09T09:17:01.637889+00:00

cnvd-2021-17268

EUVD-2026-25016

2026-10-09T09:17:01.637924+00:00

EUVD-2026-25016

fkie_cve-2021-26308

2026-10-09T09:17:01.637939+00:00

An issue was discovered in the marc crate before 2.0.0 for Rust. A user-provided Read implementation can gain access to the old contents of newly allocated memory, violating soundness.

GHSA-3mf3-2gv9-h39j — Uninitialized buffer use in marc

2026-10-09T09:17:01.637968+00:00

Affected: crates.io: marc

Affected versions of this crate passes an uninitialized buffer to a user-provided Read implementation. (Record::read()). 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. This flaw was fixed in commit 6299af0 by zero-initializing the newly allocated memory (via data.resize(len, 0)) instead of exposing uninitialized memory (unsafe { data.set_len(len) }).

gsd-2021-26308

2026-10-09T09:17:01.637994+00:00

gsd-2021-26308

RUSTSEC-2021-0014 — Record::read : Custom `Read` on uninitialized buffer may cause UB

2026-10-09T09:17:01.638006+00:00

Affected: crates.io: marc

Affected versions of this crate passes an uninitialized buffer to a user-provided `Read` implementation. (`Record::read()`)

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.

This flaw was fixed in commit 6299af0 by zero-initializing the newly allocated memory (via `data.resize(len, 0)`) instead of exposing uninitialized memory (`unsafe { data.set_len(len) }`).