Filtered by vendor Wolfssl
Subscriptions
Filtered by product Wolfssl
Subscriptions
Total
51 CVE
CVE | Vendors | Products | Updated | CVSS v3.1 |
---|---|---|---|---|
CVE-2021-38597 | 1 Wolfssl | 1 Wolfssl | 2021-08-23 | 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-37155 | 1 Wolfssl | 1 Wolfssl | 2021-07-29 | 9.8 Critical |
wolfSSL 4.6.x through 4.7.x before 4.8.0 does not produce a failure outcome when the serial number in an OCSP request differs from the serial number in the OCSP response. | ||||
CVE-2021-24116 | 1 Wolfssl | 1 Wolfssl | 2021-07-22 | 4.9 Medium |
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 single stepped, especially Intel SGX. | ||||
CVE-2020-12457 | 1 Wolfssl | 1 Wolfssl | 2021-07-21 | 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-2019-14317 | 1 Wolfssl | 1 Wolfssl | 2021-07-21 | 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-2019-19962 | 1 Wolfssl | 1 Wolfssl | 2021-07-21 | 7.5 High |
wolfSSL before 4.3.0 mishandles calls to wc_SignatureGenerateHash, leading to fault injection in RSA cryptography. | ||||
CVE-2020-11735 | 1 Wolfssl | 1 Wolfssl | 2021-07-21 | 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-2021-3336 | 1 Wolfssl | 1 Wolfssl | 2021-03-04 | 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 | 2021-01-12 | 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-24613 | 1 Wolfssl | 1 Wolfssl | 2020-09-01 | 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-24585 | 1 Wolfssl | 1 Wolfssl | 2020-08-26 | 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-2019-6439 | 1 Wolfssl | 1 Wolfssl | 2020-08-24 | N/A |
examples/benchmark/tls_bench.c in a benchmark tool in wolfSSL through 3.15.7 has a heap-based buffer overflow. | ||||
CVE-2014-2896 | 1 Wolfssl | 1 Wolfssl | 2020-02-04 | 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-2014-2897 | 1 Wolfssl | 1 Wolfssl | 2020-02-04 | 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-2898 | 1 Wolfssl | 1 Wolfssl | 2020-02-04 | 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-2019-19963 | 1 Wolfssl | 1 Wolfssl | 2020-01-02 | 5.3 Medium |
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-19960 | 1 Wolfssl | 1 Wolfssl | 2020-01-02 | 5.3 Medium |
In wolfSSL before 4.3.0, wc_ecc_mulmod_ex does not properly resist side-channel attacks. | ||||
CVE-2014-2901 | 1 Wolfssl | 1 Wolfssl | 2019-12-04 | 7.5 High |
wolfssl before 3.2.0 does not properly issue certificates for a server's hostname. | ||||
CVE-2014-2902 | 1 Wolfssl | 1 Wolfssl | 2019-12-04 | 7.5 High |
wolfssl before 3.2.0 does not properly authorize CA certificate for signing other certificates. | ||||
CVE-2014-2904 | 1 Wolfssl | 1 Wolfssl | 2019-12-04 | 7.5 High |
wolfssl before 3.2.0 has a server certificate that is not properly authorized for server authentication. |