Filtered by vendor Wolfssl
Subscribe
Total
63 CVE
CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
---|---|---|---|---|---|
CVE-2021-45934 | 1 Wolfssl | 1 Wolfmqtt | 2024-02-04 | 4.3 MEDIUM | 5.5 MEDIUM |
wolfSSL wolfMQTT 1.9 has a heap-based buffer overflow in MqttClient_DecodePacket (called from MqttClient_HandlePacket and MqttClient_WaitType). | |||||
CVE-2021-45932 | 1 Wolfssl | 1 Wolfmqtt | 2024-02-04 | 4.3 MEDIUM | 5.5 MEDIUM |
wolfSSL wolfMQTT 1.9 has a heap-based buffer overflow (4 bytes) in MqttDecode_Publish (called from MqttClient_DecodePacket and MqttClient_HandlePacket). | |||||
CVE-2021-38597 | 1 Wolfssl | 1 Wolfssl | 2024-02-04 | 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-24116 | 1 Wolfssl | 1 Wolfssl | 2024-02-04 | 4.0 MEDIUM | 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-2021-37155 | 1 Wolfssl | 1 Wolfssl | 2024-02-04 | 7.5 HIGH | 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-2020-36177 | 1 Wolfssl | 1 Wolfssl | 2024-02-04 | 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-2021-3336 | 1 Wolfssl | 1 Wolfssl | 2024-02-04 | 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-24585 | 1 Wolfssl | 1 Wolfssl | 2024-02-04 | 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-24613 | 1 Wolfssl | 1 Wolfssl | 2024-02-04 | 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-12457 | 1 Wolfssl | 1 Wolfssl | 2024-02-04 | 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-11735 | 1 Wolfssl | 1 Wolfssl | 2024-02-04 | 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-2020-11713 | 1 Wolfssl | 1 Wolfssl | 2024-02-04 | 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-15309 | 1 Wolfssl | 1 Wolfssl | 2024-02-04 | 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-2014-2896 | 1 Wolfssl | 1 Wolfssl | 2024-02-04 | 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-2014-2902 | 1 Wolfssl | 1 Wolfssl | 2024-02-04 | 5.0 MEDIUM | 7.5 HIGH |
wolfssl before 3.2.0 does not properly authorize CA certificate for signing other certificates. | |||||
CVE-2019-19960 | 1 Wolfssl | 1 Wolfssl | 2024-02-04 | 4.3 MEDIUM | 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 | 2024-02-04 | 5.0 MEDIUM | 7.5 HIGH |
wolfssl before 3.2.0 does not properly issue certificates for a server's hostname. | |||||
CVE-2019-19962 | 1 Wolfssl | 1 Wolfssl | 2024-02-04 | 5.0 MEDIUM | 7.5 HIGH |
wolfSSL before 4.3.0 mishandles calls to wc_SignatureGenerateHash, leading to fault injection in RSA cryptography. | |||||
CVE-2014-2904 | 1 Wolfssl | 1 Wolfssl | 2024-02-04 | 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-16748 | 1 Wolfssl | 1 Wolfssl | 2024-02-04 | 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. |