2021

An issue was discovered in the nalgebra crate before 0.27.1 for Rust. It allows out-of-bounds memory access because it d

An issue was discovered in the lettre crate before 0.9.6 for Rust. In an e-mail message body, an attacker can place a .

An issue was discovered in the iced-x86 crate through 1.10.3 for Rust. In Decoder::new(), slice.get_unchecked(slice.leng

An issue was discovered in the anymap crate through 0.12.1 for Rust. It violates soundness via conversion of a *u8 to a

An issue was discovered in the comrak crate before 0.10.1 for Rust. It mishandles & characters, leading to XSS via &# HT

Go before 1.15.15 and 1.16.x before 1.16.7 has a race condition that can lead to a net/http/httputil ReverseProxy panic

An issue was discovered in the max7301 crate before 0.2.0 for Rust. The ImmediateIO and TransactionalIO types implement

An issue was discovered in the generator crate before 0.7.0 for Rust. It does not ensure that a function (for yielding v

An issue was discovered in the disrustor crate through 2020-12-17 for Rust. RingBuffer doe not properly limit the number

An issue was discovered in the appendix crate through 2020-11-15 for Rust. For the generic K and V type parameters, Send

An issue was discovered in the cgc crate through 2020-12-10 for Rust. Ptr::write performs non-atomic write operations on

An issue was discovered in the cgc crate through 2020-12-10 for Rust. Ptr::get returns more than one mutable reference t

An issue was discovered in the cgc crate through 2020-12-10 for Rust. Ptr implements Send and Sync for all types.

An issue was discovered in the generic-array crate before 0.13.3 for Rust. It violates soundness by using the arr! macro

An issue was discovered in the heapless crate before 0.6.1 for Rust. The IntoIter Clone implementation clones an entire

An issue was discovered in the multiqueue crate through 2020-12-25 for Rust. There are unconditional implementations of

An issue was discovered in the syncpool crate before 0.1.6 for Rust. There is an unconditional implementation of Send fo

An issue was discovered in the noise_search crate through 2020-12-10 for Rust. There are unconditional implementations o

An issue was discovered in the model crate through 2020-11-10 for Rust. The Shared data structure has an implementation

An issue was discovered in the dces crate through 2020-12-09 for Rust. The World type is marked as Send but lacks bounds

An issue was discovered in the lexer crate through 2020-11-10 for Rust. For ReaderResult<T, E>, there is an implementati

An issue was discovered in the lever crate before 0.1.1 for Rust. AtomicBox<T> implements the Send and Sync traits for a

An issue was discovered in the toolshed crate through 2020-11-15 for Rust. In CopyCell<T>, the Send trait lacks bounds o

An issue was discovered in the slock crate through 2020-11-17 for Rust. Slock<T> unconditionally implements Send and Syn

An issue was discovered in the parc crate through 2020-11-14 for Rust. LockWeak<T> has an unconditional implementation o

An issue was discovered in the scottqueue crate through 2020-11-15 for Rust. There are unconditional implementations of

An issue was discovered in the array-tools crate before 0.3.2 for Rust. FixedCapacityDequeLike::clone() has a drop of un

An issue was discovered in the rcu_cell crate through 2020-11-14 for Rust. There are unconditional implementations of Se

An issue was discovered in the bunch crate through 2020-11-12 for Rust. There are unconditional implementations of Send

An issue was discovered in the kekbit crate before 0.3.4 for Rust. For ShmWriter<H>, Send is implemented without requiri

An issue was discovered in the cache crate through 2020-11-24 for Rust. There are unconditional implementations of Send

An issue was discovered in the v9 crate through 2020-12-18 for Rust. There is an unconditional implementation of Sync fo

An issue was discovered in the signal-simple crate through 2020-11-15 for Rust. There are unconditional implementations

An issue was discovered in the convec crate through 2020-11-24 for Rust. There are unconditional implementations of Send

An issue was discovered in the async-coap crate through 2020-12-08 for Rust. Send and Sync are implemented for ArcGuard<

An issue was discovered in the libp2p-deflate crate before 0.27.1 for Rust. An uninitialized buffer is passed to AsyncRe

An issue was discovered in the beef crate before 0.5.0 for Rust. beef::Cow has no Sync bound on its Send trait.

An issue was discovered in the abox crate before 0.4.1 for Rust. It implements Send and Sync for AtomicBox<T> with no re

An issue was discovered in the libsbc crate before 0.1.5 for Rust. For Decoder<R>, it implements Send for any R: Read.

An issue was discovered in the ticketed_lock crate before 0.3.0 for Rust. There are unconditional implementations of Sen

An issue was discovered in the tiny_future crate before 0.4.0 for Rust. Future<T> does not have bounds on its Send and S

An issue was discovered in the conqueue crate before 0.4.0 for Rust. There are unconditional implementations of Send and

An issue was discovered in the unicycle crate before 0.7.1 for Rust. PinSlab<T> and Unordered<T, S> do not have bounds o

An issue was discovered in the ruspiro-singleton crate before 0.4.1 for Rust. In Singleton, Send and Sync do not have bo

An issue was discovered in the sys-info crate before 0.8.0 for Rust. sys_info::disk_info calls can trigger a double free

An issue was discovered in the chunky crate through 2020-08-25 for Rust. The Chunk API does not honor an alignment requi

An issue was discovered in the alg_ds crate through 2020-08-25 for Rust. There is a drop of uninitialized memory in Matr

GNU cpio through 2.13 allows attackers to execute arbitrary code via a crafted pattern file, because of a dstring.c ds_f

Btrbk before 0.31.2 allows command execution because of the mishandling of remote hosts filtering SSH commands using ssh

Roxy-WI through 5.2.2.0 allows command injection via /app/funct.py and /api/api_funct.py.