From 2e4cdf36d0955f8f2c5288c0175dfcec93eac859 Mon Sep 17 00:00:00 2001 From: Youngsuk Kim Date: Sat, 21 Aug 2021 21:33:07 -0400 Subject: [PATCH] csv-sniffer: reading on uninitialized memory may cause undefined behavior (#666) * Report 0092-csv-sniffer to RustSec * informational = "unsound" --- crates/csv-sniffer/RUSTSEC-0000-0000.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 crates/csv-sniffer/RUSTSEC-0000-0000.md diff --git a/crates/csv-sniffer/RUSTSEC-0000-0000.md b/crates/csv-sniffer/RUSTSEC-0000-0000.md new file mode 100644 index 0000000..0a26ca0 --- /dev/null +++ b/crates/csv-sniffer/RUSTSEC-0000-0000.md @@ -0,0 +1,19 @@ +```toml +[advisory] +id = "RUSTSEC-0000-0000" +package = "csv-sniffer" +date = "2021-01-05" +url = "https://github.com/jblondin/csv-sniffer/issues/1" +categories = ["memory-exposure"] +informational = "unsound" + +[versions] +patched = [] +``` + +# `Read` on uninitialized memory may cause UB (fn preamble_skipcount()) + +Affected versions of this crate passes an uninitialized buffer to a user-provided `Read` implementation (within `fn preamble_skipcount()`). + +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.