Risk of buffer overflow in PyString::from_object

Potential out-of-bounds read with a malformed ELF file and the HashTable API.

ssl::select_next_proto use after free

Segmentation fault due to lack of bound check

Segmentation fault due to lack of bound check

ruzstd uninit and out-of-bounds memory reads

Usage of non-constant time base64 decoder could lead to leakage of secret key material

Degraded secret zeroization capabilities

Non-idiomatic use of iterators leads to use after free

Use-after-free when setting the locale

Default functions in VolatileMemory trait lack bounds checks, potentially leading to out-of-bounds memory accesses

openssl X509VerifyParamRef::set_host buffer over-read

Versionize::deserialize implementation for FamStructWrapper<T> is lacking bound checks, potentially leading to out of bounds memory accesses

Possible out-of-bounds read in release mode

X.509 Name Constraints Read Buffer Overflow

X.400 address type confusion in X.509 GeneralName

tokio::io::ReadHalf<T>::unsplit is Unsound

Use-after-free due to a lifetime error in Vec::into_iter()

Bug in Wasmtime implementation of pooling instance allocator

Bug in pooling instance allocator

out-of-bounds read possible when setting list-of-pointers

Use after free in MacOS / iOS implementation

Incorrect use of set_len allows for un-initialized memory

Use of uninitialized memory in temporary

Use after free in Neon external buffers

array! macro is unsound when its length is impure constant

Use after free with externrefs and epoch interruption in Wasmtime

enum_map macro can cause UB when Enum trait is incorrectly implemented

Unsoundness in dashmap references

DecimalArray does not perform bound checks on accessing values and offsets

FixedSizeBinaryArray does not perform bound checks on accessing values and offsets

BinaryArray does not perform bound checks on reading values and offsets

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

Memory Safety Issue when using patch or merge on state and assign the result back to state

Multiple Vulnerabilities in Wasmtime

Reading on uninitialized memory may cause UB ( util::read_spv() )

Window can read out of bounds if Read instance returns more bytes than buffer size

'Read' on uninitialized memory may cause UB

Read on uninitialized buffer can cause UB (impl of ReadKVExt)

mopa is technically unsound

Read on uninitialized buffer may cause UB ( read_entry() )

read on uninitialized buffer may cause UB (bite::read::BiteReadExpandedExt::read_framed_max)

columnar: Read on uninitialized buffer may cause UB (ColumnarReadExt::read_typed_vec())

Deserialization functions pass uninitialized memory to user-provided Read

Reading on uninitialized buffer may cause UB ( gfx_auxil::read_spirv() )

Read on uninitialized memory may cause UB (fn preamble_skipcount())

Read on uninitialized buffer in fill_buf() and read_up_to()

InputStream::read_exact : Read on uninitialized buffer causes UB

API soundness issue in join() implementation of [Borrow<str>]

vec_deque::Iter has unsound Debug implementation

VecStorage Deserialize Allows Violation of Length Invariant

Memory access due to code generation flaw in Cranelift module

Archives may contain uninitialized memory

KeyValueReader passes uninitialized memory to Read instance

PartialReader passes uninitialized memory to user-provided Read

Tape::take_bytes exposes uninitialized memory to a user-provided Read

Use-after-free when cloning a partially consumed Vec iterator

Multiple soundness issues

Read on uninitialized buffer may cause UB (impl Walue for Vec<u8>)

IoReader::read(): user-provided Read on uninitialized buffer may cause UB

Sectors::get accesses unclaimed/uninitialized memory

Contents of uninitialized memory exposed in DeflateOutput's AsyncRead implementation

Record::read : Custom Read on uninitialized buffer may cause UB

Reading uninitialized memory can cause UB (Deserializer::read_vec)

reading on uninitialized buffer can cause UB (impl<R> BufRead for GreedyAccessReader<R>)

Frame::copy_from_raw_parts can lead to segfault without unsafe

rio allows a use-after-free buffer access when a future is leaked

sigstack allocation bug can cause memory corruption or leak

Flaw in realloc allows reading unknown memory