158 matches found
UBUNTU-CVE-2021-26958
An issue was discovered in the xcb crate through 2021-02-04 for Rust. It has a soundness violation because transmutation to the wrong type can happen after xcb::base::castevent uses std::mem::transmute to return a reference to an arbitrary type...
Use after free possible in `uri::Formatter` on panic
Affected versions of this crate transmuted a &str to a &'static str before pushing it into a StackVec, this value was then popped later in the same function. This was assumed to be safe because the reference would be valid while the method's stack was active. In between the push and the pop,...
CVE-2021-26306
An issue was discovered in the raw-cpuid crate before 9.0.0 for Rust. It has unsound transmute calls within asstring methods...
CVE-2021-26306
An issue was discovered in the raw-cpuid crate before 9.0.0 for Rust. It has unsound transmute calls within asstring methods...
Code injection
An issue was discovered in the raw-cpuid crate before 9.0.0 for Rust. It has unsound transmute calls within asstring methods...
CVE-2021-26306
CVE-2021-26306 affects the Rust crate raw-cpuid prior to version 9.0.0. The issue is caused by unsound transmute usage in as_string() methods, which leads to undefined behavior when converting data from #[repr(Rust)] structs via byte slices (VendorInfo.as_string(), SoCVendorBrand::as_string(), Ex...
CVE-2021-26306
An issue was discovered in the raw-cpuid crate before 9.0.0 for Rust. It has unsound transmute calls within asstring methods...
CVE-2020-35864
An issue was discovered in the flatbuffers crate through 2020-04-11 for Rust. readscalar and readscalarat can transmute values without unsafe blocks...
CVE-2020-35864
An issue was discovered in the flatbuffers crate through 2020-04-11 for Rust. readscalar and readscalarat can transmute values without unsafe blocks...
CVE-2018-21000
An issue was discovered in the safe-transmute crate before 0.10.1 for Rust. A constructor's arguments are in the wrong order, causing heap memory corruption...
CVE-2018-21000
An issue was discovered in the safe-transmute crate before 0.10.1 for Rust. A constructor's arguments are in the wrong order, causing heap memory corruption...
UBUNTU-CVE-2018-21000
An issue was discovered in the safe-transmute crate before 0.10.1 for Rust. A constructor's arguments are in the wrong order, causing heap memory corruption...
Memory corruption
An issue was discovered in the safe-transmute crate before 0.10.1 for Rust. A constructor's arguments are in the wrong order, causing heap memory corruption...
CVE-2018-21000
An issue was discovered in the safe-transmute crate before 0.10.1 for Rust. A constructor's arguments are in the wrong order, causing heap memory corruption...
CVE-2018-21000
An issue was discovered in the safe-transmute crate before 0.10.1 for Rust. A constructor's arguments are in the wrong order, causing heap memory corruption...
CVE-2018-21000
CVE-2018-21000 affects the Rust crate safe-transmute prior to 0.10.1. The issue is that a constructor’s arguments are provided in the wrong order, leading to heap memory corruption. This can result in memory corruption or data leakage as described in multiple sources. There is no exploitation det...
CVE-2018-21000
An issue was discovered in the safe-transmute crate before 0.10.1 for Rust. A constructor's arguments are in the wrong order, causing heap memory corruption...
nifti (>=0.3.1, <=0.6.0), trk-io (>=0.3.0, <=0.11.0) potentially affected by CVE-2018-21000 via safe-transmute (>=0.5.0, <=0.8.0)
safe-transmute CARGO version =0.5.0, =0.3.1, =0.3.0, =0.11.0 Source cves: CVE-2018-21000 Source advisory: OSV:RUSTSEC-2018-0013...