You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello 🦀,
we (Rust group @sslab-gatech) found a memory-safety/soundness issue in this crate while scanning Rust code on crates.io for potential vulnerabilities.
let n_read = stream.read(&mut buf[n_saved_bytes..])?;
XdvParser::<T>::process() method creates an uninitialized buffer and passes it to user-provided Read implementation. This is unsound, because it allows safe Rust code to exhibit an undefined behavior (read from uninitialized memory).
This part from the Read trait documentation explains the issue:
It is your responsibility to make sure that buf is initialized before calling read. Calling read with an uninitialized buf (of the kind one obtains via MaybeUninit<T>) is not safe, and can lead to undefined behavior.
How to fix the issue?
The Naive & safe way to fix the issue is to always zero-initialize a buffer before lending it to a user-provided Read implementation. Note that this approach will add runtime performance overhead of zero-initializing the buffer.
As of Feb 2021, there is not yet an ideal fix that works with no performance overhead. Below are links to relevant discussions & suggestions for the fix.
Thank you for filing this. I've read about this topic since I wrote this code but forgot that I had this implementation in here. I'm looking forward to the day that there's a nicer Rust solution for avoiding this unsoundness issue, but in the meantime, it is totally fine to fix this by zeroing out the buffer. I'll prepare a PR to do so.
It took a long time, but now there is both a fixed version of tectonic_xdv release, and the new 0.5.0 release of tectonic is based on that version of the crate.
Hello 🦀,
we (Rust group @sslab-gatech) found a memory-safety/soundness issue in this crate while scanning Rust code on crates.io for potential vulnerabilities.
Issue Description
tectonic/crates/xdv/src/lib.rs
Lines 224 to 231 in 28a9b46
XdvParser::<T>::process()
method creates an uninitialized buffer and passes it to user-providedRead
implementation. This is unsound, because it allows safe Rust code to exhibit an undefined behavior (read from uninitialized memory).This part from the
Read
trait documentation explains the issue:How to fix the issue?
The Naive & safe way to fix the issue is to always zero-initialize a buffer before lending it to a user-provided
Read
implementation. Note that this approach will add runtime performance overhead of zero-initializing the buffer.As of Feb 2021, there is not yet an ideal fix that works with no performance overhead. Below are links to relevant discussions & suggestions for the fix.
The text was updated successfully, but these errors were encountered: