Skip to content
OpenAdvisories

Ecosystem

crates.io

2,075 known vulnerabilities.

196 results · Clear filters · Feed

  • Critical 9.8

    Use after free and double free in bitvec

    An issue was discovered in the bitvec crate before 0.17.4 for Rust. BitVec to BitBox conversion leads to a use-after-free or double free.

  • Critical 9.8

    HTTP Request Smuggling in hyper

    An issue was discovered in the hyper crate before 0.12.34 for Rust. HTTP request smuggling can occur. Remote code execution can occur in certain situations with an HTTP server on the loopback interface.

  • Critical 9.8

    Data races in rusqlite

    An issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated via VTab / VTabCursor.

  • Critical 9.8

    Use after free in rio

    An issue was discovered in the rio crate through 2020-05-11 for Rust. A struct can be leaked, allowing attackers to obtain sensitive information, cause a use-after-free, or cause a data race.

  • Critical 9.8

    Drop of uninitialized memory in Ozone

    An issue was discovered in the ozone crate through 2020-07-04 for Rust. Memory safety is violated because of out-of-bounds access.

  • Critical 9.8

    Data races in rulinalg

    An issue was discovered in the rulinalg crate through 2020-02-11 for Rust. There are incorrect lifetime-boundary definitions for RowMut::raw_slice and RowMut::raw_slice_mut.

  • Critical 9.8

    Unsoundness in bigint

    An issue was discovered in the bigint crate through 2020-05-07 for Rust. It allows a soundness violation.

  • Critical 9.8

    Out of bounds write in traitobject

    An issue was discovered in the traitobject crate through 2020-06-01 for Rust. It has false expectations about fat pointers, possibly causing memory corruption in, for example, Rust 2.x.

  • Critical 9.1

    Path traversal in mozwire

    An issue was discovered in the mozwire crate through 2020-08-18 for Rust. A ../ directory-traversal situation allows overwriting local files that have .conf at the end of the filename.

  • Critical 9.8

    Double free in alpm-rs

    An issue was discovered in the alpm-rs crate through 2020-08-20 for Rust. StrcCtx performs improper memory deallocation.

  • Critical 9.8

    Multiple security issues including data race, buffer overflow, and uninitialized memory drop in arr

    An issue was discovered in the arr crate through 2020-08-25 for Rust. An attacker can smuggle non-Sync/Send types across a thread boundary to cause a data race.

  • Critical 9.1

    Out of bounds read in simple-slab

    An issue was discovered in the simple-slab crate before 0.3.3 for Rust. index() allows an out-of-bounds read.

  • Critical 9.8

    Out-of-bounds write in stack

    An issue was discovered in the stack crate before 0.3.1 for Rust. ArrayVec has an out-of-bounds write via element insertion.

  • Critical 9.1

    Use after free in actix-utils

    An issue was discovered in the actix-utils crate before 2.0.0 for Rust. The Cell implementation allows obtaining more than one mutable reference to the same data.

  • Critical 9.8

    Use-after-free in actix-codec

    An issue was discovered in the actix-codec crate before 0.3.0-beta.1 for Rust. There is a use-after-free in Framed.

  • Critical 9.8

    Access of Uninitialized Pointer in linked-hash-map

    An issue was discovered in the linked-hash-map crate before 0.5.3 for Rust. It creates an uninitialized NonNull pointer, which violates a non-null constraint.

  • Critical 9.8

    Unaligned memory access in rand_core

    An issue was discovered in the rand_core crate before 0.4.2 for Rust. Casting of byte slices to integer slices mishandles alignment constraints.

  • Critical 9.1

    Out of bounds access in rgb

    A safety violation was discovered in the rgb crate before 0.8.20 for Rust, leading to (for example) dereferencing of arbitrary pointers or disclosure of uninitialized memory. This occurs because structs can be treated as bytes for read and write operations.

  • Critical 9.8

    Use after free in portaudio-rs

    An issue was discovered in the portaudio-rs crate through 0.3.1 for Rust. There is a use-after-free with resultant arbitrary code execution because of a lack of unwind safety in stream_callback and stream_finished_callback.

  • Critical 9.8

    Double free in linea

    An issue was discovered in the linea crate through 0.9.4 for Rust. There is double free in the Matrix::zip_elements method.

  • Critical 9.8

    Algorithms compute incorrect results in blake2

    An issue was discovered in the blake2 crate before 0.8.1 for Rust. The BLAKE2b and BLAKE2s algorithms, when used with HMAC, produce incorrect results because the block sizes are half of the required sizes.

  • Critical 9.8

    Improper Input Validation in renderdoc

    An issue was discovered in the renderdoc crate before 0.5.0 for Rust. Multiple exposed methods take self by immutable reference, which is incompatible with a multi-threaded application.

  • Critical 9.8

    Out of bounds access in compact_arena

    An issue was discovered in the compact_arena crate before 0.4.0 for Rust. Generativity is mishandled, leading to an out-of-bounds write or read.

  • Critical 9.8

    Use after free in image

    An issue was discovered in the image crate before 0.21.3 for Rust, affecting the HDR image format decoder. Vec::set_len is called on an uninitialized vector, leading to a use-after-free and arbitrary code execution.

  • Critical 9.8

    Use-after-free in chttp

    An issue was discovered in the chttp crate before 0.1.3 for Rust. There is a use-after-free during buffer conversion.

  • Critical 9.8

    Memory corruption slice-deque

    An issue was discovered in the slice-deque crate before 0.1.16 for Rust. move_head_unchecked allows memory corruption because deque updates are mishandled.

  • Critical 9.8

    Double free in crossbeam

    An issue was discovered in the crossbeam crate before 0.4.1 for Rust. There is a double free because of destructor mishandling.

  • Critical 9.8

    Use after free in openssl

    An issue was discovered in the openssl crate before 0.10.9 for Rust. A use-after-free occurs in CMS Signing.

  • Critical 9.8

    Potential memory corruption in arrayfire

    An issue was discovered in the arrayfire crate before 3.6.0 for Rust. Addition of the repr() attribute to an enum is mishandled, leading to memory corruption.

  • Critical 9.8

    Out of bounds write in slice-deque

    An issue was discovered in the slice-deque crate before 0.2.0 for Rust. There is memory corruption in certain allocation cases.

  • Critical 9.8

    Use after free in libflate

    An issue was discovered in the libflate crate before 0.1.25 for Rust. MultiDecoder::read has a use-after-free, leading to arbitrary code execution.

  • Critical 9.8

    Double free in smallvec

    An issue was discovered in the smallvec crate before 0.6.10 for Rust. There is a double free for certain grow attempts with the current capacity.

  • Critical 9.8

    Memory corruption in smallvec

    An issue was discovered in the smallvec crate before 0.6.10 for Rust. There is memory corruption for certain grow attempts with less than the current capacity.

  • Critical 9.8

    Heap overflow or corruption in safe-transmute

    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.

  • Critical 9.8

    Double free in smallvec

    An issue was discovered in the smallvec crate before 0.6.3 for Rust. The Iterator implementation mishandles destructors, leading to a double free.

  • Critical 9.8

    Integer overflow in base64

    rust-base64 version <= 0.5.1 is vulnerable to a buffer overflow when calculating the size of a buffer to use when encoding base64 using the 'encode_config_buf' and 'encode_config' functions