Browse
Advisories from RustSec Advisory Database
1,483 advisories, most recently modified first.
RustSec Advisory Database (CC0 1.0). Source
- Medium RUSTSEC-2020-0059 MutexGuard::map can cause a data race in safe code
- High RUSTSEC-2020-0060 futures_task::waker may cause a use-after-free if used on a type that isn't 'static
- Medium RUSTSEC-2020-0061 futures_task::noop_waker_ref can segfault due to dereferencing a NULL pointer
- Medium RUSTSEC-2020-0062 Improper Sync implementation on FuturesUnordered in futures-utils can cause data corruption
- High RUSTSEC-2020-0068 Unexpected panic in multihash from_slice parsing code
- Critical RUSTSEC-2020-0021 rio allows a use-after-free buffer access when a future is leaked
- Critical RUSTSEC-2020-0022 Ozone contains several memory safety issues
- Critical RUSTSEC-2020-0023 Lifetime boundary for raw_slice and raw_slice_mut are incorrect
- Critical RUSTSEC-2020-0025 bigint is unmaintained, use uint instead
- Critical RUSTSEC-2020-0027 traitobject assumes the layout of fat pointers
- High RUSTSEC-2020-0028 LocalRequest::clone creates multiple mutable references to the same object
- Critical RUSTSEC-2020-0030 Missing sanitization in mozwire allows local file overwrite of files ending in .conf
- Medium RUSTSEC-2020-0031 HTTP Request smuggling through malformed Transfer Encoding headers
- Critical RUSTSEC-2020-0032 StrcCtx deallocates a memory region that it doesn't own
- High RUSTSEC-2020-0037 Misbehaving HandleLike implementation can lead to memory safety violation
- High RUSTSEC-2020-0038 Memory safety issues in compact::Vec
- RUSTSEC-2020-0039 index() allows out-of-bound read and remove() has off-by-one error
- High RUSTSEC-2020-0040 Obstack generates unaligned references
- Critical RUSTSEC-2020-0042 Missing check in ArrayVec leads to out-of-bounds write.
- Critical RUSTSEC-2020-0005 CBox API allows to de-reference raw pointers without unsafe code
- High RUSTSEC-2020-0006 Flaw in realloc allows reading unknown memory
- Critical RUSTSEC-2020-0007 use-after or double free of allocated memory
- Critical RUSTSEC-2020-0008 Flaw in hyper allows request smuggling by sending a body in GET requests
- High RUSTSEC-2020-0009 read_scalar and read_scalar_at allow transmuting values without unsafe blocks
- High RUSTSEC-2020-0012 Relies on undefined behavior of char::from_u32_unchecked
- High RUSTSEC-2020-0017 Use after free in ArcIntern::drop
- High RUSTSEC-2020-0019 tokio-rustls reads may cause excessive memory usage
- High RUSTSEC-2020-0001 Stack overflow when resolving additional records from MX or SRV null targets
- Critical RUSTSEC-2020-0004 sigstack allocation bug can cause memory corruption or leak
- High RUSTSEC-2020-0091 Dangling reference in access::Map with Constant
- Medium RUSTSEC-2020-0069 Argument injection in sendmail transport
- Medium RUSTSEC-2021-0001 XSS in mdBook's search page
- RUSTSEC-2020-0093 Async-h1 request smuggling possible with long unread bodies
- Critical RUSTSEC-2019-0035 Unaligned memory access
- Critical RUSTSEC-2020-0026 linked-hash-map creates uninitialized NonNull pointer
- Critical RUSTSEC-2020-0029 Allows viewing and modifying arbitrary structs as bytes
- RUSTSEC-2020-0052 Undefined Behavior in bounded channel
- High RUSTSEC-2020-0157 Improper Synchronization and Race Condition in vm-memory
- High RUSTSEC-2019-0027 Flaw in Scalar::check_overflow allows side-channel timing attack
- Critical RUSTSEC-2019-0028 Unsound impl Follow for bool
- High RUSTSEC-2019-0029 ChaCha20 counter overflow can expose repetitions in the keystream
- RUSTSEC-2019-0030 Incorrect implementation of the Streebog hash functions
- High RUSTSEC-2019-0033 Integer Overflow in HeaderMap::reserve() can cause Denial of Service
- Critical RUSTSEC-2019-0034 HeaderMap::Drain API is unsound
- Critical RUSTSEC-2019-0036 Type confusion if private_get_type_id is overridden
- Medium RUSTSEC-2019-0037 Compiler optimisation for next_with_timeout in pnet::transport::IcmpTransportChannelIterator flaws to SEGFAULT
- RUSTSEC-2019-0038 Fix for UB in failure to catch panics crossing FFI boundaries
- High RUSTSEC-2019-0025 Flaw in CBOR deserializer allows stack overflow
- Critical RUSTSEC-2019-0026 generichash::Digest::eq always return true
- Medium RUSTSEC-2020-0156 Observable Discrepancy in libsecp256k1-rs
- Critical RUSTSEC-2019-0021 Matrix::zip_elements causes double free
- Critical RUSTSEC-2019-0022 Stream callback function is not unwind safe
- High RUSTSEC-2019-0023 Cloned interners may read already dropped strings
- High RUSTSEC-2019-0013 Wrong memory orderings in RwLock potentially violates mutual exclusion
- Critical RUSTSEC-2019-0014 Flaw in interface may drop uninitialized instance of arbitrary types
- Critical RUSTSEC-2019-0015 Flaw in generativity allows out-of-bounds access
- Critical RUSTSEC-2019-0016 Use-after-free in buffer conversion implementation
- High RUSTSEC-2019-0017 Panic during initialization of Lazy<T> might trigger undefined behavior
- Critical RUSTSEC-2019-0018 Internally mutating methods take immutable ref self
- Critical RUSTSEC-2019-0019 HMAC-BLAKE2 algorithms compute incorrect results
- High RUSTSEC-2019-0020 fix unsound APIs that could lead to UB
- High RUSTSEC-2019-0007 Processing of maliciously crafted length fields causes memory allocation SIGABRTs
- High RUSTSEC-2019-0008 Flaw in string parsing can lead to crashes due to invalid memory access.
- Critical RUSTSEC-2019-0010 MultiDecoder::read() drops uninitialized memory of arbitrary type on panic in client code
- High RUSTSEC-2019-0011 Flaw in offset_of and span_of causes SIGILL, drops uninitialized memory of arbitrary type on panic in client code
- High RUSTSEC-2019-0001 Uncontrolled recursion leads to abort in HTML serialization
- High RUSTSEC-2019-0003 Out of Memory in stream::read_raw_bytes_into()
- High RUSTSEC-2019-0004 Failure to properly verify ed25519 signatures makes any signature valid
- High RUSTSEC-2019-0005 Format string vulnerabilities in pancurses
- RUSTSEC-2019-0006 Buffer overflow and format vulnerabilities in functions exposed without unsafe
- RUSTSEC-2018-0018 smallvec creates uninitialized value of any type
- High RUSTSEC-2018-0001 An integer underflow could lead to panic
- High RUSTSEC-2018-0002 Links in archives can overwrite any existing file
- Medium RUSTSEC-2018-0004 Malicious input could cause uninitialized memory to be exposed
- High RUSTSEC-2018-0006 Uncontrolled recursion leads to abort in deserialization
- High RUSTSEC-2018-0007 Stack overflow when parsing malicious DNS packet
- Critical RUSTSEC-2018-0010 Use after free in CMS Signing
- High RUSTSEC-2018-0012 Flaw in streaming state reset() functions can create incorrect results.
- Critical RUSTSEC-2018-0013 Vec-to-vec transmutations could lead to heap overflow/corruption
- Medium RUSTSEC-2017-0002 headers containing newline characters can split messages
- Medium RUSTSEC-2017-0003 Hostname verification skipped when custom root certs used
- High RUSTSEC-2017-0005 Large cookie Max-Age values can cause a denial of service
- Critical RUSTSEC-2017-0004 Integer overflow leads to heap-based buffer overflow in encode_config_buf
- Medium RUSTSEC-2017-0001 scalarmult() vulnerable to degenerate public keys
- Medium RUSTSEC-2016-0003 HTTP download and execution allows MitM RCE
- High RUSTSEC-2021-0041 Denial of service through parsing payloads with too big exponent
- RUSTSEC-2023-0067 fehler is unmaintained; use culpa instead
- RUSTSEC-2021-0139 ansi_term is Unmaintained
- RUSTSEC-2022-0081 json is unmaintained
- RUSTSEC-2023-0040 users crate is unmaintained
- RUSTSEC-2023-0051 dlopen_derive is unmaintained
- RUSTSEC-2023-0050 multipart is Unmaintained
- RUSTSEC-2023-0049 tui is unmaintained; use ratatui instead
- RUSTSEC-2023-0043 ftp is unmaintained, use suppaftp instead
- RUSTSEC-2023-0019 kuchiki is unmaintained
- RUSTSEC-2023-0037 crate has been renamed to crypto_secretbox
- RUSTSEC-2023-0036 tree_magic is Unmaintained
- RUSTSEC-2023-0028 buf_redux is Unmaintained
- RUSTSEC-2023-0025 Gitoxide has renamed its crates.
- RUSTSEC-2023-0026 Gitoxide has renamed its crates.