VYPR

Wolfssl

by WolfSSL

Source repositories

CVEs (154)

  • CVE-2026-5263MedApr 9, 2026
    risk 0.35cvss 6.5epss 0.00

    URI nameConstraints from constrained intermediate CAs are parsed but not enforced during certificate chain verification in wolfcrypt/src/asn.c. A compromised or malicious sub-CA could issue leaf certificates with URI SAN entries that violate the nameConstraints of the issuing…

  • CVE-2025-12889MedNov 22, 2025
    risk 0.35cvss 5.4epss 0.00

    With TLS 1.2 connections a client can use any digest, specifically a weaker digest that is supported, rather than those in the CertificateRequest.

  • CVE-2022-42961MedOct 15, 2022
    risk 0.35cvss 5.3epss 0.01

    An issue was discovered in wolfSSL before 5.5.0. A fault injection attack on RAM via Rowhammer leads to ECDSA key disclosure. Users performing signing operations with private ECC keys, such as in server-side TLS connections, might leak faulty ECC signatures. These signatures can…

  • CVE-2020-24585MedAug 21, 2020
    risk 0.35cvss 5.3epss 0.01

    An issue was discovered in the DTLS handshake implementation in wolfSSL before 4.5.0. Clear DTLS application_data messages in epoch 0 do not produce an out-of-order error. Instead, these messages are returned to the application.

  • CVE-2020-11735MedJun 25, 2020
    risk 0.35cvss 5.3epss 0.01

    The private-key operations in ecc.c in wolfSSL before 4.4.0 do not use a constant-time modular inverse when mapping to affine coordinates, aka a "projective coordinates leak."

  • CVE-2019-19963MedDec 25, 2019
    risk 0.35cvss 5.3epss 0.01

    An issue was discovered in wolfSSL before 4.3.0 in a non-default configuration where DSA is enabled. DSA signing uses the BEEA algorithm during modular inversion of the nonce, leading to a side-channel attack against the nonce.

  • CVE-2019-19960MedDec 25, 2019
    risk 0.35cvss 5.3epss 0.01

    In wolfSSL before 4.3.0, wc_ecc_mulmod_ex does not properly resist side-channel attacks.

  • CVE-2019-14317MedDec 11, 2019
    risk 0.35cvss 5.3epss 0.02

    wolfSSL and wolfCrypt 4.1.0 and earlier (formerly known as CyaSSL) generate biased DSA nonces. This allows a remote attacker to compute the long term private key from several hundred DSA signatures via a lattice attack. The issue occurs because dsa.c fixes two bits of the…

  • CVE-2025-11936MedNov 21, 2025
    risk 0.34cvss 5.3epss 0.00

    Improper input validation in the TLS 1.3 KeyShareEntry parsing in wolfSSL v5.8.2 on multiple platforms allows a remote unauthenticated attacker to cause a denial-of-service by sending a crafted ClientHello message containing duplicate KeyShareEntry values for the same supported…

  • CVE-2024-5814MedAug 27, 2024
    risk 0.34cvss 5.3epss 0.00

    A malicious TLS1.2 server can force a TLS1.3 client with downgrade capability to use a ciphersuite that it did not agree to and achieve a successful connection. This is because, aside from the extensions, the client was skipping fully parsing the server hello. …

  • CVE-2024-5288MedAug 27, 2024
    risk 0.33cvss 5.1epss 0.00

    An issue was discovered in wolfSSL before 5.7.0. A safe-error attack via Rowhammer, namely FAULT+PROBE, leads to ECDSA key disclosure. When WOLFSSL_CHECK_SIG_FAULTS is used in signing operations with private ECC keys, such as in server-side TLS connections, the connection is…

  • CVE-2021-24116MedJul 14, 2021
    risk 0.32cvss 4.9epss 0.01

    In wolfSSL through 4.6.0, a side-channel vulnerability in base64 PEM file decoding allows system-level (administrator) attackers to obtain information about secret RSA keys via a controlled-channel and side-channel attack on software running in isolated environments that can be…

  • CVE-2026-5500MedApr 10, 2026
    risk 0.31cvss 5.9epss 0.00

    wolfSSL's wc_PKCS7_DecodeAuthEnvelopedData() does not properly sanitize the AES-GCM authentication tag length received and has no lower bounds check. A man-in-the-middle can therefore truncate the mac field from 16 bytes to 1 byte, reducing the tag check from 2⁻¹²⁸ to…

  • CVE-2026-3579MedMar 19, 2026
    risk 0.31cvss 5.9epss 0.00

    wolfSSL 5.8.4 on RISC-V RV32I architectures lacks a constant-time software implementation for 64-bit multiplication. The compiler-inserted __muldi3 subroutine executes in variable time based on operand values. This affects multiple SP math functions (sp_256_mul_9, sp_256_sqr_9,…

  • CVE-2019-13628MedOct 3, 2019
    risk 0.31cvss 4.7epss 0.00

    wolfSSL and wolfCrypt 4.0.0 and earlier (when configured without --enable-fpecc, --enable-sp, or --enable-sp-math) contain a timing side channel in ECDSA signature generation. This allows a local attacker, able to precisely measure the duration of signature operations, to infer…

  • CVE-2018-12436MedJun 15, 2018
    risk 0.31cvss 4.7epss 0.00

    wolfcrypt/src/ecc.c in wolfSSL before 3.15.1.patch allows a memory-cache side-channel attack on ECDSA signatures, aka the Return Of the Hidden Number Problem or ROHNP. To discover an ECDSA key, the attacker needs access to either the local machine or a different virtual machine…

  • CVE-2025-7396MedJul 18, 2025
    risk 0.30cvss 4.6epss 0.00

    In wolfSSL release 5.8.2 blinding support is turned on by default for Curve25519 in applicable builds. The blinding configure option is only for the base C implementation of Curve25519. It is not needed, or available with; ARM assembly builds, Intel assembly builds, and the…

  • CVE-2026-3229MedMar 19, 2026
    risk 0.29cvss 5.5epss 0.00

    An integer overflow vulnerability existed in the static function wolfssl_add_to_chain, that caused heap corruption when certificate data was written out of bounds of an insufficiently sized certificate buffer. wolfssl_add_to_chain is called by these API:…

  • CVE-2026-94419MedSep 27, 2026
    risk 0.28cvss 5.4epss 0.00

    Without NO_SESSION_CACHE_REF, wolfSSL_get_session() does not return a session object but a ClientSession reference of the form {row, index, hash(sessionID)} into the process-global SessionCache, and ClientSessionToSession() validates it against that hash alone. Because the TLS…

  • CVE-2026-5392MedApr 10, 2026
    risk 0.28cvss 5.4epss 0.00

    Heap out-of-bounds read in PKCS7 parsing. A crafted PKCS7 message can trigger an OOB read on the heap. The missing bounds check is in the indefinite-length end-of-content verification loop in PKCS7_VerifySignedData().

Page 6 of 8