Filtered by vendor Wolfssl
Subscribe
Total
59 CVE
CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
---|---|---|---|---|---|
CVE-2021-38597 | 1 Wolfssl | 1 Wolfssl | 2023-12-10 | 4.3 MEDIUM | 5.9 MEDIUM |
wolfSSL before 4.8.1 incorrectly skips OCSP verification in certain situations of irrelevant response data that contains the NoCheck extension. | |||||
CVE-2021-3336 | 1 Wolfssl | 1 Wolfssl | 2023-12-10 | 6.8 MEDIUM | 8.1 HIGH |
DoTls13CertificateVerify in tls13.c in wolfSSL before 4.7.0 does not cease processing for certain anomalous peer behavior (sending an ED22519, ED448, ECC, or RSA signature without the corresponding certificate). The client side is affected because man-in-the-middle attackers can impersonate TLS 1.3 servers. | |||||
CVE-2020-36177 | 1 Wolfssl | 1 Wolfssl | 2023-12-10 | 10.0 HIGH | 9.8 CRITICAL |
RsaPad_PSS in wolfcrypt/src/rsa.c in wolfSSL before 4.6.0 has an out-of-bounds write for certain relationships between key size and digest size. | |||||
CVE-2020-15309 | 1 Wolfssl | 1 Wolfssl | 2023-12-10 | 6.9 MEDIUM | 7.0 HIGH |
An issue was discovered in wolfSSL before 4.5.0, when single precision is not employed. Local attackers can conduct a cache-timing attack against public key operations. These attackers may already have obtained sensitive information if the affected system has been used for private key operations (e.g., signing with a private key). | |||||
CVE-2020-24585 | 1 Wolfssl | 1 Wolfssl | 2023-12-10 | 5.0 MEDIUM | 5.3 MEDIUM |
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-11713 | 1 Wolfssl | 1 Wolfssl | 2023-12-10 | 5.0 MEDIUM | 7.5 HIGH |
wolfSSL 4.3.0 has mulmod code in wc_ecc_mulmod_ex in ecc.c that does not properly resist timing side-channel attacks. | |||||
CVE-2020-12457 | 1 Wolfssl | 1 Wolfssl | 2023-12-10 | 5.0 MEDIUM | 7.5 HIGH |
An issue was discovered in wolfSSL before 4.5.0. It mishandles the change_cipher_spec (CCS) message processing logic for TLS 1.3. If an attacker sends ChangeCipherSpec messages in a crafted way involving more than one in a row, the server becomes stuck in the ProcessReply() loop, i.e., a denial of service. | |||||
CVE-2020-24613 | 1 Wolfssl | 1 Wolfssl | 2023-12-10 | 4.9 MEDIUM | 6.8 MEDIUM |
wolfSSL before 4.5.0 mishandles TLS 1.3 server data in the WAIT_CERT_CR state, within SanityCheckTls13MsgReceived() in tls13.c. This is an incorrect implementation of the TLS 1.3 client state machine. This allows attackers in a privileged network position to completely impersonate any TLS 1.3 servers, and read or modify potentially sensitive information between clients using the wolfSSL library and these TLS servers. | |||||
CVE-2020-11735 | 1 Wolfssl | 1 Wolfssl | 2023-12-10 | 5.0 MEDIUM | 5.3 MEDIUM |
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-14317 | 1 Wolfssl | 1 Wolfssl | 2023-12-10 | 4.3 MEDIUM | 5.3 MEDIUM |
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 generated nonces. | |||||
CVE-2014-2896 | 1 Wolfssl | 1 Wolfssl | 2023-12-10 | 7.5 HIGH | 9.8 CRITICAL |
The DoAlert function in the (1) TLS and (2) DTLS implementations in wolfSSL CyaSSL before 2.9.4 allows remote attackers to have unspecified impact and vectors, which trigger memory corruption or an out-of-bounds read. | |||||
CVE-2019-13628 | 1 Wolfssl | 1 Wolfssl | 2023-12-10 | 1.2 LOW | 4.7 MEDIUM |
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 information about the nonces used and potentially mount a lattice attack to recover the private key used. The issue occurs because ecc.c scalar multiplication might leak the bit length. | |||||
CVE-2014-2897 | 1 Wolfssl | 1 Wolfssl | 2023-12-10 | 7.5 HIGH | 9.8 CRITICAL |
The SSL 3 HMAC functionality in wolfSSL CyaSSL 2.5.0 before 2.9.4 does not check the padding length when verification fails, which allows remote attackers to have unspecified impact via a crafted HMAC, which triggers an out-of-bounds read. | |||||
CVE-2014-2901 | 1 Wolfssl | 1 Wolfssl | 2023-12-10 | 5.0 MEDIUM | 7.5 HIGH |
wolfssl before 3.2.0 does not properly issue certificates for a server's hostname. | |||||
CVE-2019-18840 | 1 Wolfssl | 1 Wolfssl | 2023-12-10 | 5.0 MEDIUM | 7.5 HIGH |
In wolfSSL 4.1.0 through 4.2.0c, there are missing sanity checks of memory accesses in parsing ASN.1 certificate data while handshaking. Specifically, there is a one-byte heap-based buffer overflow inside the DecodedCert structure in GetName in wolfcrypt/src/asn.c because the domain name location index is mishandled. Because a pointer is overwritten, there is an invalid free. | |||||
CVE-2019-16748 | 1 Wolfssl | 1 Wolfssl | 2023-12-10 | 7.5 HIGH | 9.8 CRITICAL |
In wolfSSL through 4.1.0, there is a missing sanity check of memory accesses in parsing ASN.1 certificate data while handshaking. Specifically, there is a one-byte heap-based buffer over-read in CheckCertSignature_ex in wolfcrypt/src/asn.c. | |||||
CVE-2014-2898 | 1 Wolfssl | 1 Wolfssl | 2023-12-10 | 7.5 HIGH | 9.8 CRITICAL |
wolfSSL CyaSSL before 2.9.4 allows remote attackers to have unspecified impact via multiple calls to the CyaSSL_read function which triggers an out-of-bounds read when an error occurs, related to not checking the return code and MAC verification failure. | |||||
CVE-2014-2904 | 1 Wolfssl | 1 Wolfssl | 2023-12-10 | 5.0 MEDIUM | 7.5 HIGH |
wolfssl before 3.2.0 has a server certificate that is not properly authorized for server authentication. | |||||
CVE-2019-19962 | 1 Wolfssl | 1 Wolfssl | 2023-12-10 | 5.0 MEDIUM | 7.5 HIGH |
wolfSSL before 4.3.0 mishandles calls to wc_SignatureGenerateHash, leading to fault injection in RSA cryptography. | |||||
CVE-2019-19960 | 1 Wolfssl | 1 Wolfssl | 2023-12-10 | 4.3 MEDIUM | 5.3 MEDIUM |
In wolfSSL before 4.3.0, wc_ecc_mulmod_ex does not properly resist side-channel attacks. |