Most recent entries from all

cnvd-2022-03127

2026-10-07T20:21:15.491468+00:00

cnvd-2022-03127

EUVD-2026-33524

2026-10-07T20:21:15.491501+00:00

EUVD-2026-33524

fkie_cve-2021-45703

2026-10-07T20:21:15.491516+00:00

An issue was discovered in the tectonic_xdv crate before 0.1.12 for Rust. XdvParser::::process may read from uninitialized memory locations.

GHSA-qwvx-c8j7-5g75 — Use of Uninitialized Resource in tectonic_xdv

2026-10-07T20:21:15.491545+00:00

Affected: crates.io: tectonic_xdv

Affected versions of this crate passes an uninitialized buffer to a user-provided Read implementation.

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.

The problem was fixed in commit `cdff034` by zero-initializing the buffer before passing it to a user-provided Read implementation.

gsd-2021-45703

2026-10-07T20:21:15.491572+00:00

gsd-2021-45703

RUSTSEC-2021-0112 — `Read` on uninitialized buffer may cause UB ('tectonic_xdv' crate)

2026-10-07T20:21:15.491584+00:00

Affected: crates.io: tectonic_xdv

Affected versions of this crate passes an uninitialized buffer to a user-provided `Read` implementation.

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.

The problem was fixed in commit `cdff034` by zero-initializing the buffer before passing it to a user-provided `Read` implementation.