Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Read on uninitialized buffer may cause UB ('tectonic_xdv' crate) #752

Closed
JOE1994 opened this issue Feb 18, 2021 · 3 comments
Closed

Read on uninitialized buffer may cause UB ('tectonic_xdv' crate) #752

JOE1994 opened this issue Feb 18, 2021 · 3 comments

Comments

@JOE1994
Copy link

JOE1994 commented Feb 18, 2021

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

let mut buf = Vec::with_capacity(BUF_SIZE);
unsafe {
buf.set_len(BUF_SIZE);
}
let mut n_saved_bytes = 0;
loop {
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.

@pkgw
Copy link
Collaborator

pkgw commented Feb 18, 2021

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.

@ammaraskar
Copy link

Has there been a release of tectonic_xdv with this fix incorporated? If not, could you make one please. Thank you!

@pkgw
Copy link
Collaborator

pkgw commented Jun 6, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants