Duplicate Advisory: `Read` on uninitialized buffer may cause UB ('tectonic_xdv' crate)
High severity
GitHub Reviewed
Published
Jun 17, 2022
to the GitHub Advisory Database
•
Updated Feb 3, 2026
Withdrawn
This advisory was withdrawn on Feb 3, 2026
Description
Published to the GitHub Advisory Database
Jun 17, 2022
Reviewed
Jun 17, 2022
Withdrawn
Feb 3, 2026
Last updated
Feb 3, 2026
Duplicate Advisory
This advisory has been withdrawn because it is a duplicate of GHSA-qwvx-c8j7-5g75. This link is maintained to preserve external references.
Original Description
Affected versions of this crate passes an uninitialized buffer to a user-provided
Readimplementation.Arbitrary
Readimplementations 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
cdff034by zero-initializing the buffer before passing it to a user-providedReadimplementation.References