`Read` on uninitialized buffer may cause UB ( `read_entry()` )
High severity
GitHub Reviewed
Published
Jun 16, 2022
to the GitHub Advisory Database
•
Updated Jan 12, 2023
Description
Published to the GitHub Advisory Database
Jun 16, 2022
Reviewed
Jun 16, 2022
Last updated
Jan 12, 2023
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.
References