From 3a073396ba6d8163b42b8745af2a75ccb89dc78d Mon Sep 17 00:00:00 2001 From: nabijaczleweli Date: Sat, 2 Mar 2019 17:32:29 +0100 Subject: [PATCH] Add safe_transmute vec2vec transmutation bug Ref: https://github.com/nabijaczleweli/safe-transmute-rs/pull/36 --- crates/safe-transmute/RUSTSEC-0000-0000.toml | 22 ++++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 crates/safe-transmute/RUSTSEC-0000-0000.toml diff --git a/crates/safe-transmute/RUSTSEC-0000-0000.toml b/crates/safe-transmute/RUSTSEC-0000-0000.toml new file mode 100644 index 0000000..5227fd9 --- /dev/null +++ b/crates/safe-transmute/RUSTSEC-0000-0000.toml @@ -0,0 +1,22 @@ +[advisory] +id = "RUSTSEC-0000-0000" +package = "safe-transmute" +date = "2019-03-02" + +title = "Vec-to-vec transmutations could lead to heap overflow/corruption" +description = """ +Affected versions of this crate switched the length and capacity arguments in the Vec::from_raw_parts() constructor, +which could lead to memory corruption or data leakage. + +The flaw was corrected by using the constructor correctly. +""" + +patched_versions = [">= 0.10.1"] +unaffected_versions = ["< 0.4.0"] + +url = "https://github.com/nabijaczleweli/safe-transmute-rs/pull/36" + +keywords = ["memory-corruption"] + +affected_functions = ["safe_transmute::guarded_transmute_vec_permissive", + "safe_transmute::guarded_transmute_to_bytes_vec"]