Read on uninitialized buffer may cause UB ( BlobReader::<R>::read_blob() )

[JOE1994]

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

rust-osm-pbf-iter/src/blob_reader.rs

Lines 35 to 41 in cb7a8bd

	let mut header_buf = Vec::with_capacity(len);
	unsafe { header_buf.set_len(len); }
	match read.read_exact(&mut header_buf) {
	Ok(()) => (),
	_ => return None
	};

rust-osm-pbf-iter/src/blob_reader.rs

Lines 47 to 53 in cb7a8bd

	let mut blob_buf = Vec::with_capacity(datasize);
	unsafe { blob_buf.set_len(datasize); }
	match read.read_exact(&mut blob_buf) {
	Ok(()) => (),
	_ => return None
	};

BlobReader::<R>::read_blob() method creates an uninitialized buffer and passes it to user-provided Read implementation (two times within the same function). 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 Jan 2021, there is not yet an ideal fix that works in stable Rust with no performance overhead. Below are links to relevant discussions & suggestions for the fix.

• Well-written document regarding the issue
• Rust RFC 2930
• nightly feature std::io::Initializer
• Discussion in Rust Internals Forum