Browse
Advisories from RustSec Advisory Database
1,483 advisories, most recently modified first.
RustSec Advisory Database (CC0 1.0). Source
- High RUSTSEC-2021-0035 quinn invalidly assumes the memory layout of std::net::SocketAddr
- Medium RUSTSEC-2021-0026 XSS in comrak
- Critical RUSTSEC-2021-0021 nb-connect invalidly assumes the memory layout of std::net::SocketAddr
- Critical RUSTSEC-2021-0022 Use-after-free in subscript_next and subscript_prev wrappers
- Critical RUSTSEC-2021-0023 Incorrect check on buffer length when seeding RNGs
- Medium RUSTSEC-2021-0018 insert_slice_clone can double drop if Clone panics.
- Critical RUSTSEC-2021-0015 Sectors::get accesses unclaimed/uninitialized memory
- High RUSTSEC-2021-0016 IoReader::read(): user-provided Read on uninitialized buffer may cause UB
- High RUSTSEC-2021-0017 Read on uninitialized buffer may cause UB (impl Walue for Vec<u8>)
- Critical RUSTSEC-2021-0012 Reading uninitialized memory can cause UB (Deserializer::read_vec)
- RUSTSEC-2021-0013 Soundness issues in raw-cpuid
- High RUSTSEC-2021-0014 Record::read : Custom Read on uninitialized buffer may cause UB
- Medium RUSTSEC-2021-0004 Missing Send bound for Lazy
- High RUSTSEC-2021-0005 Double drop upon panic in 'fn map_array()'
- High RUSTSEC-2021-0006 Exposes internally used raw pointer
- High RUSTSEC-2021-0007 Frame::copy_from_raw_parts can lead to segfault without unsafe
- Critical RUSTSEC-2021-0008 reading on uninitialized buffer can cause UB (impl<R> BufRead for GreedyAccessReader<R>)
- High RUSTSEC-2021-0009 panic safety issue in impl TransformContent<S, D> for [S; (2|3|4)]
- Critical RUSTSEC-2021-0010 panic safety: double drop may happen within util::{mutate, mutate2}
- High RUSTSEC-2021-0011 EventList's From<EventList> conversions can double drop on panic.
- Medium RUSTSEC-2021-0058 Null pointer deref in X509_issuer_and_serial_hash()
- Medium RUSTSEC-2021-0143 kamadak-exif DoS with untrusted PNG data
- RUSTSEC-2020-0153 read on uninitialized buffer may cause UB (bite::read::BiteReadExpandedExt::read_framed_max)
- RUSTSEC-2020-0154 InputStream::read_exact : Read on uninitialized buffer causes UB
- RUSTSEC-2020-0155 Read on uninitialized buffer in fill_buf() and read_up_to()
- High RUSTSEC-2020-0137 AtomicBox<T> lacks bound on its Send and Sync traits allowing data races
- High RUSTSEC-2020-0138 ReaderResult should be bounded by Sync
- High RUSTSEC-2020-0139 dces' World type can cause data races
- High RUSTSEC-2020-0140 Shared can cause a data race
- High RUSTSEC-2020-0141 MvccRwLock allows data races & aliasing violations
- High RUSTSEC-2020-0142 Send bound needed on T (for Send impl of Bucket2)
- High RUSTSEC-2020-0143 Queues allow non-Send types to be sent to other threads, allowing data races
- High RUSTSEC-2020-0145 Use-after-free when cloning a partially consumed Vec iterator
- High RUSTSEC-2020-0146 arr! macro erases lifetimes
- Medium RUSTSEC-2020-0149 Data race and memory safety issue in Index
- Medium RUSTSEC-2020-0150 RingBuffer can create multiple mutable references and cause data races
- Medium RUSTSEC-2020-0151 Generators can cause data races if non-Send types are used in their generator functions
- Medium RUSTSEC-2020-0152 ImmediateIO and TransactionalIO can cause data races
- High RUSTSEC-2020-0121 AtomicBox<T> implements Send/Sync for any T: Sized
- High RUSTSEC-2020-0122 beef::Cow lacks a Sync bound on its Send trait allowing for data races
- Critical RUSTSEC-2020-0123 Contents of uninitialized memory exposed in DeflateOutput's AsyncRead implementation
- High RUSTSEC-2020-0124 ArcGuard's Send and Sync should have bounds on RC
- High RUSTSEC-2020-0125 convec::ConVec<T> unconditionally implements Send/Sync
- High RUSTSEC-2020-0126 SyncChannel<T> can move 'T: !Send' to other threads
- High RUSTSEC-2020-0127 SyncRef's clone() and debug() allow data races
- High RUSTSEC-2020-0128 Cache<K>: Send/Sync impls needs trait bounds on K
- High RUSTSEC-2020-0129 ShmWriter allows sending non-Send type across threads
- High RUSTSEC-2020-0130 Bunch<T> unconditionally implements Send/Sync
- High RUSTSEC-2020-0131 Send/Sync bound needed on T for Send/Sync impl of RcuCell<T>
- Critical RUSTSEC-2020-0132 FixedCapacityDequeLike::clone() can cause dropping uninitialized memory
- High RUSTSEC-2020-0133 Queue<T> should have a Send bound on its Send/Sync traits
- High RUSTSEC-2020-0134 LockWeak<T> allows to create data race to T.
- High RUSTSEC-2020-0135 Slock<T> allows sending non-Send types across thread boundaries
- High RUSTSEC-2020-0136 CopyCell lacks bounds on its Send trait allowing for data races
- Critical RUSTSEC-2020-0033 Matrix::new() drops uninitialized memory
- High RUSTSEC-2020-0035 Chunk API does not respect align requirement
- Critical RUSTSEC-2020-0100 Double free when calling sys_info::disk_info from multiple threads
- High RUSTSEC-2020-0115 Singleton lacks bounds on Send and Sync.
- High RUSTSEC-2020-0116 PinSlab<T> and Unordered<T, S> need bounds on their Send/Sync traits
- High RUSTSEC-2020-0117 QueueSender<T>/QueueReceiver<T>: Send/Sync impls need T: Send
- High RUSTSEC-2020-0118 Future<T> lacks bounds on Send and Sync.
- High RUSTSEC-2020-0119 ReadTicket and WriteTicket should only be sendable when T is Send
- High RUSTSEC-2020-0120 Decoder<R> can carry R: !Send to other threads
- Medium RUSTSEC-2020-0108 Soundness issue: Input<R> can be misused to create data race to an object
- Medium RUSTSEC-2020-0112 ButtplugFutureStateShared allows data race to (!Send|!Sync) objects
- Medium RUSTSEC-2020-0113 AtomicOption should have Send + Sync bound on its type argument.
- Medium RUSTSEC-2020-0114 Demuxer can carry non-Send types across thread boundaries
- Medium RUSTSEC-2020-0094 Unsound: can make ARefss contain a !Send, !Sync object.
- Medium RUSTSEC-2020-0096 TreeFocus lacks bounds on its Send and Sync traits
- Medium RUSTSEC-2020-0097 Soundness issue with base::Error
- High RUSTSEC-2020-0098 UsbContext trait did not require implementers to be Send and Sync.
- High RUSTSEC-2020-0099 Aovec<T> lacks bound on its Send and Sync traits allowing data races
- High RUSTSEC-2020-0101 conquer-once's OnceCell lacks Send bound for its Sync trait.
- High RUSTSEC-2020-0102 LateStatic has incorrect Sync bound
- High RUSTSEC-2020-0103 impl Random on arrays can lead to dropping uninitialized memory
- High RUSTSEC-2020-0104 ImageChunkMut needs bounds on its Send and Sync traits
- High RUSTSEC-2020-0105 Update unsound DrainFilter and RString::retain
- Medium RUSTSEC-2020-0106 Queues allow non-Send types to be sent to other threads, allowing data races
- High RUSTSEC-2020-0107 hashconsing's HConsed lacks Send/Sync bound for its Send/Sync trait.
- Medium RUSTSEC-2020-0072 GenericMutexGuard allows data races of non-Sync types across threads
- Medium RUSTSEC-2020-0073 Mutable reference with immutable provenance
- Medium RUSTSEC-2020-0074 Reference counting error in From<Py<T>>
- Medium RUSTSEC-2020-0075 Unexpected panic when decoding tokens
- Medium RUSTSEC-2020-0078 net2 invalidly assumes the memory layout of std::net::SocketAddr
- Medium RUSTSEC-2020-0080 miow invalidly assumes the memory layout of std::net::SocketAddr
- Medium RUSTSEC-2020-0081 mio invalidly assumes the memory layout of std::net::SocketAddr
- Medium RUSTSEC-2020-0082 ordered_float:NotNan may contain NaN after panic in assignment operators
- Medium RUSTSEC-2020-0087 TryMutex<T> allows sending non-Send type across threads
- Medium RUSTSEC-2020-0088 MPMCConsumer/Producer allows sending non-Send type across threads
- Medium RUSTSEC-2020-0089 nanorand 0.5.0 - RNGs failed to generate properly for non-64-bit numbers
- Medium RUSTSEC-2020-0090 Thex<T> allows data races of non-Send types across threads
- Medium RUSTSEC-2020-0092 Send/Sync bound needed on V in impl Send/Sync for ARCache<K, V>
- High RUSTSEC-2020-0043 Insufficient size checks in outgoing buffer in ws allows remote attacker to run the process out of memory
- Medium RUSTSEC-2020-0044 Unsafe Send implementation in Atom allows data races
- Critical RUSTSEC-2020-0045 bespoke Cell implementation allows obtaining several mutable references to the same data
- Medium RUSTSEC-2020-0046 bespoke Cell implementation allows obtaining several mutable references to the same data
- Medium RUSTSEC-2020-0047 array_queue pop_back() may cause a use-after-free
- High RUSTSEC-2020-0048 Use-after-free in BodyStream due to lack of pinning
- Critical RUSTSEC-2020-0049 Use-after-free in Framed due to lack of pinning
- Medium RUSTSEC-2020-0050 VecCopy allows misaligned access to elements