Skip to content
OpenAdvisories

Vendor

RustCrypto

11 known vulnerabilities.

5 results · Clear filters · Feed

  • Medium 5.3

    ML-DSA Signature Verification Accepts Signatures with Repeated Hint Indices

    The ML-DSA crate is a Rust implementation of the Module-Lattice-Based Digital Signature Standard (ML-DSA). Starting in version 0.0.4 and prior to version 0.1.0-rc.4, the ML-DSA signature verification implementation in the RustCrypto `ml-dsa` crate incorrectly…

  • Medium 6.4

    RustCrypto: Signatures has timing side-channel in ML-DSA decomposition

    RustCrypto: Signatures offers support for digital signatures, which provide authentication of data using public-key cryptography. Prior to version 0.1.0-rc.2, a timing side-channel was discovered in the Decompose algorithm which is used during ML-DSA signing …

  • Medium 5.6

    AEADs/ascon-aead: Plaintext exposed in decrypt_in_place_detached even on tag verification failure

    aes-gcm is a pure Rust implementation of the AES-GCM. In decrypt_in_place_detached, the decrypted ciphertext (which is the correct ciphertext) is exposed even if the tag is incorrect. This is because in decrypt_inplace in asconcore.rs, tag verification causes…

  • Medium 5.9

    RustCrypto/RSA vulnerable to a Marvin Attack via key recovery through timing sidechannels

    RustCrypto/RSA is a portable RSA implementation in pure Rust. Due to a non-constant-time implementation, information about the private key is leaked through timing information which is observable over the network. An attacker may be able to use that informati…

  • Medium 4.7

    AEADs/aes-gcm: Plaintext exposed in decrypt_in_place_detached even on tag verification failure

    aes-gcm is a pure Rust implementation of the AES-GCM. Starting in version 0.10.0 and prior to version 0.10.3, in the AES GCM implementation of decrypt_in_place_detached, the decrypted ciphertext (i.e. the correct plaintext) is exposed even if tag verification…