Skip to content
OpenAdvisories

Ecosystem

crates.io

2,075 known vulnerabilities.

2,074 results · Feed

  • Critical 9.8

    Double free in through

    An issue was discovered in the through crate through 2021-02-18 for Rust. There is a double free (in through and through_and) upon a panic of the map function.

  • High 7.3

    Out of bounds write in reorder

    An issue was discovered in the reorder crate through 2021-02-24 for Rust. swap_index has an out-of-bounds write if an iterator returns a len() that is too small.

  • High 7.4
    CVE-2021-3450 Public exploit EPSS 18%

    CA certificate check bypass with X509_V_FLAG_X509_STRICT

    The X509_V_FLAG_X509_STRICT flag enables additional security checks of the certificates present in a certificate chain. It is not set by default. Starting from OpenSSL version 1.1.1h a check to disallow certificates in the chain that have explicitly encoded e…

  • Medium 5.9
    CVE-2021-3449 Public exploit EPSS 64%

    NULL pointer deref in signature_algorithms processing

    An OpenSSL TLS server may crash if sent a maliciously crafted renegotiation ClientHello message from a client. If a TLSv1.2 renegotiation ClientHello omits the signature_algorithms extension (where it was present in the initial ClientHello), but includes a si…

  • Critical 9.8

    Fix a use-after-free bug in diesels Sqlite backend

    An issue was discovered in the diesel crate before 1.4.6 for Rust. There is a use-after-free in the SQLite backend because the semantics of sqlite3_column_name are not followed.

  • High 7.5

    Null pointer deference in fltk

    An issue was discovered in the fltk crate before 0.15.3 for Rust. There is a NULL pointer dereference during attempted use of a multi label type if the image is nonexistent.

  • Critical 9.8

    Loading a bgzip block can write out of bounds if size overflows.

    An issue was discovered in the bam crate before 0.1.3 for Rust. There is an integer underflow and out-of-bounds write during the loading of a bgzip block.

  • Critical 9.8

    Double free in toodee

    An issue was discovered in the toodee crate before 0.3.0 for Rust. Row insertion can cause a double free upon an iterator panic.

  • High 7.5

    Use of Uninitialized Resource in truetype

    An issue was discovered in the truetype crate before 0.30.1 for Rust. Attackers can read the contents of uninitialized memory locations via a user-provided Read operation within Tape::take_bytes.

  • Critical 9.8

    move_elements can double-free objects on panic

    An issue was discovered in the scratchpad crate before 1.3.1 for Rust. The move_elements function can have a double-free upon a panic in a user-provided f function.

  • Critical 9.8

    Use after free in nano_arena

    An issue was discovered in the nano_arena crate before 0.5.2 for Rust. There is an aliasing violation in split_at because two mutable references can exist for the same element, if Borrow<Idx> behaves in certain ways. This can have a resultant out-of-bounds wr…

  • Critical 9.8

    Drop of uninitialized memory in stack_dst

    An issue was discovered in the stack_dst crate before 0.6.1 for Rust. Because of the push_inner behavior, a double free can occur upon a val.clone() panic.

  • High 7.5

    quinn invalidly assumes the memory layout of std::net::SocketAddr

    An issue was discovered in the quinn crate before 0.7.0 for Rust. It may have invalid memory access for certain versions of the standard library because it relies on a direct cast of std::net::SocketAddrV4 and std::net::SocketAddrV6 data structures.

  • Critical 9.8

    Data race in internment

    An issue was discovered in the internment crate before 0.4.2 for Rust. There is a data race that can cause memory corruption because of the unconditional implementation of Sync for Intern<T>.

  • Critical 9.8

    Deserializing an array can free uninitialized memory in byte_struct

    An issue was discovered in the byte_struct crate before 0.6.1 for Rust. There can be a drop of uninitialized memory if a certain deserialization method panics.

  • Unscored —

    project abandoned; migrate to the `aes-siv` crate

    The Miscreant project has been abandoned and archived. The Rust implementation has been adapted into the new `aes-siv` crate which implements both the AES-CMAC-SIV and AES-PMAC-SIV constructions: <https://github.com/RustCrypto/AEADs/tree/master/aes-siv> Pleas…

  • Medium 6.1

    Cross site scripting in comrak

    An issue was discovered in the comrak crate before 0.9.1 for Rust. XSS can occur because the protection mechanism for data: and javascript: URIs is case-sensitive, allowing (for example) Data: to be used in an attack.

  • Critical 9.8

    nb-connect invalidly assumes the memory layout of std::net::SocketAddr

    An issue was discovered in the nb-connect crate before 1.0.3 for Rust. It may have invalid memory access for certain versions of the standard library because it relies on a direct cast of std::net::SocketAddrV4 and std::net::SocketAddrV6 data structures.

  • Critical 9.8

    Use-after-free in yottadb

    An issue was discovered in the yottadb crate before 1.2.0 for Rust. For some memory-allocation patterns, ydb_subscript_next_st and ydb_subscript_prev_st have a use-after-free.

  • Critical 9.8

    Incorrect check on buffer length in rand_core

    An issue was discovered in the rand_core crate before 0.6.2 for Rust. Because read_u32_into and read_u64_into mishandle certain buffer-length checks, a random number generator may be seeded with too little data.

  • High 7.5
    CVE-2021-23840 Public exploit EPSS 51%

    Integer overflow in CipherUpdate

    Calls to EVP_CipherUpdate, EVP_EncryptUpdate and EVP_DecryptUpdate may overflow the output length argument in some cases where the input length is close to the maximum permissable length for an integer on the platform. In such cases the return value from the …

  • Medium 5.9
    CVE-2021-23841 Public exploit

    Null pointer deref in X509_issuer_and_serial_hash()

    The OpenSSL public API function X509_issuer_and_serial_hash() attempts to create a unique hash value based on the issuer and serial number data contained within an X509 certificate. However it fails to correctly handle any errors that may occur while parsing …

  • Unscored —

    crate has been renamed to `qjsonrpc`

    This crate has been renamed from `jsonrpc-quic` to `qjsonrpc`. The new repository location is: <https://github.com/maidsafe/sn_api>

  • Unscored —

    crate has been renamed to `sn_api`

    This crate has been renamed from `safe-api` to `sn_api`. The new repository location is: <https://github.com/maidsafe/sn_api>

  • Medium 4.8

    Multiple Transfer-Encoding headers misinterprets request payload

    hyper is an open-source HTTP library for Rust (crates.io). In hyper from version 0.12.0 and before versions 0.13.10 and 0.14.3 there is a vulnerability that can enable a request smuggling attack. The HTTP server code had a flaw that incorrectly understands so…

  • Critical 9.8

    Out of bounds write in calamine

    An issue was discovered in the calamine crate before 0.17.0 for Rust. It allows attackers to overwrite heap-memory locations because Vec::set_len is used without proper memory claiming, and this uninitialized memory is used for a user-provided Read operation,…

  • High 7.5

    Use of Uninitialized Resource in ms3d

    An issue was discovered in the ms3d crate before 0.1.3 for Rust. It might allow attackers to obtain sensitive information from uninitialized memory locations via IoReader::read.

  • Medium 5.3

    insert_slice_clone can double drop if Clone panics.

    An issue was discovered in the qwutils crate before 0.3.1 for Rust. When a Clone panic occurs, insert_slice_clone can perform a double drop.

  • Critical 9.8

    Out of bounds read in xcb

    An issue was discovered in the xcb crate through 2021-02-04 for Rust. It has a soundness violation because xcb::xproto::GetAtomNameReply::name() calls std::str::from_utf8_unchecked() on unvalidated bytes from an X server.

  • High 7.5

    Read on uninitialized buffer in postscript

    An issue was discovered in the postscript crate before 0.14.0 for Rust. It might allow attackers to obtain sensitive information from uninitialized memory locations via a user-provided Read implementation.

  • Unscored —

    office is unmaintained, use calamine instead

    The `office` crate is unmaintained. Use [calamine](https://crates.io/crates/calamine) for reading excel files. Contact the `office` author for ownership of the package name.

  • Unscored —

    ncollide2d is unmaintained

    The maintainer has advised that this crate is passively-maintained and that it is being superseded by the [Parry](https://github.com/dimforge/parry) project.

  • Unscored —

    ncollide3d is unmaintained

    The maintainer has advised that this crate is passively-maintained and that it is being superseded by the [Parry](https://github.com/dimforge/parry) project.

  • Unscored —

    nphysics2d is unmaintained

    The maintainer has advised that this crate is passively-maintained and that it is being superseded by the [Rapier](https://github.com/dimforge/rapier) project.

  • Unscored —

    nphysics3d is unmaintained

    The maintainer has advised that this crate is passively-maintained and that it is being superseded by the [Rapier](https://github.com/dimforge/rapier) project.

  • Critical 9.8

    Read of uninitialized memory in cdr

    An issue was discovered in Deserializer::read_vec in the cdr crate before 0.2.4 for Rust. A user-provided Read implementation can gain access to the old contents of newly allocated heap memory, violating soundness.

  • High 7.5

    Soundness issue in raw-cpuid

    An issue was discovered in the raw-cpuid crate before 9.0.0 for Rust. It has unsound transmute calls within as_string() methods.

  • High 7.5

    Uninitialized buffer use in marc

    An issue was discovered in the marc crate before 2.0.0 for Rust. A user-provided Read implementation can gain access to the old contents of newly allocated memory, violating soundness.

  • Medium 4.7

    Data races in reffers

    An issue was discovered in the reffers crate through 2020-12-01 for Rust. ARefss can contain a !Send,!Sync object, leading to a data race and memory corruption.

  • Medium 4.7

    Data races in im

    An issue was discovered in the im crate through 2020-11-09 for Rust. Because TreeFocus does not have bounds on its Send trait or Sync trait, a data race can occur.