Debian Wolfssl vulnerabilities

CVE-2022-23408 [CRITICAL] CVE-2022-23408: wolfssl - wolfSSL 5.x before 5.1.1 uses non-random IV values in certain situations. This a... wolfSSL 5.x before 5.1.1 uses non-random IV values in certain situations. This affects connections (without AEAD) using AES-CBC or DES3 with TLS 1.1 or 1.2 or DTLS 1.1 or 1.2. This occurs because of misplaced memory initialization in BuildMessage in internal.c. Scope: local bookworm: resolved (fixed in 5.1.1-1) bullseye: resolved forky: resolved (fixed in 5.1.1-

CVE-2022-25640 [HIGH] CVE-2022-25640: wolfssl - In wolfSSL before 5.2.0, a TLS 1.3 server cannot properly enforce a requirement ... In wolfSSL before 5.2.0, a TLS 1.3 server cannot properly enforce a requirement for mutual authentication. A client can simply omit the certificate_verify message from the handshake, and never present a certificate. Scope: local bookworm: resolved (fixed in 5.2.0-1) bullseye: resolved (fixed in 4.6.0+p1-0+deb11u1) forky: resolved (fixed in 5.2.0-1) sid: resolved (fi

CVE-2022-38152 [HIGH] CVE-2022-38152: wolfssl - An issue was discovered in wolfSSL before 5.5.0. When a TLS 1.3 client connects ... An issue was discovered in wolfSSL before 5.5.0. When a TLS 1.3 client connects to a wolfSSL server and SSL_clear is called on its session, the server crashes with a segmentation fault. This occurs in the second session, which is created through TLS session resumption and reuses the initial struct WOLFSSL. If the server reuses the previous session structure (struct

CVE-2022-39173 [HIGH] CVE-2022-39173: wolfssl - In wolfSSL before 5.5.1, malicious clients can cause a buffer overflow during a ... In wolfSSL before 5.5.1, malicious clients can cause a buffer overflow during a TLS 1.3 handshake. This occurs when an attacker supposedly resumes a previous TLS session. During the resumption Client Hello a Hello Retry Request must be triggered. Both Client Hellos are required to contain a list of duplicate cipher suites to trigger the buffer overflow. In total, tw

CVE-2022-34293 [HIGH] CVE-2022-34293: wolfssl - wolfSSL before 5.4.0 allows remote attackers to cause a denial of service via DT... wolfSSL before 5.4.0 allows remote attackers to cause a denial of service via DTLS because a check for return-routability can be skipped. Scope: local bookworm: resolved (fixed in 5.5.3-1) bullseye: open forky: resolved (fixed in 5.5.3-1) sid: resolved (fixed in 5.5.3-1) trixie: resolved (fixed in 5.5.3-1)

CVE-2022-25638 [MEDIUM] CVE-2022-25638: wolfssl - In wolfSSL before 5.2.0, certificate validation may be bypassed during attempted... In wolfSSL before 5.2.0, certificate validation may be bypassed during attempted authentication by a TLS 1.3 client to a TLS 1.3 server. This occurs when the sig_algo field differs between the certificate_verify message and the certificate message. Scope: local bookworm: resolved (fixed in 5.2.0-1) bullseye: resolved (fixed in 4.6.0+p1-0+deb11u1) forky: resolved (

CVE-2022-38153 [MEDIUM] CVE-2022-38153: wolfssl - An issue was discovered in wolfSSL before 5.5.0 (when --enable-session-ticket is... An issue was discovered in wolfSSL before 5.5.0 (when --enable-session-ticket is used); however, only version 5.3.0 is exploitable. Man-in-the-middle attackers or a malicious server can crash TLS 1.2 clients during a handshake. If an attacker injects a large ticket (more than 256 bytes) into a NewSessionTicket message in a TLS 1.2 handshake, and the client has a n

CVE-2022-42961 [MEDIUM] CVE-2022-42961: wolfssl - An issue was discovered in wolfSSL before 5.5.0. A fault injection attack on RAM... 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 be processed via an advanced technique for ECDSA key recovery. (In 5.5.0 and later, WO

CVE-2021-37155 [CRITICAL] CVE-2021-37155: wolfssl - wolfSSL 4.6.x through 4.7.x before 4.8.0 does not produce a failure outcome when... 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. Scope: local bookworm: resolved (fixed in 5.0.0-1) bullseye: resolved (fixed in 4.6.0+p1-0+deb11u1) forky: resolved (fixed in 5.0.0-1) sid: resolved (fixed in 5.0.0-1) trixie: resolved (fixed i

CVE-2021-3336 [HIGH] CVE-2021-3336: wolfssl - DoTls13CertificateVerify in tls13.c in wolfSSL before 4.7.0 does not cease proce... 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. Scope: local bookworm: resolved (fixed in 4.6.0-3) bullseye:

CVE-2021-24116 [MEDIUM] CVE-2021-24116: wolfssl - In wolfSSL through 4.6.0, a side-channel vulnerability in base64 PEM file decodi... 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. Scope: local bookworm: resolved (fixed in 4.6.0-1

CVE-2021-38597 [MEDIUM] CVE-2021-38597: wolfssl - wolfSSL before 4.8.1 incorrectly skips OCSP verification in certain situations o... wolfSSL before 4.8.1 incorrectly skips OCSP verification in certain situations of irrelevant response data that contains the NoCheck extension. Scope: local bookworm: resolved (fixed in 5.0.0-1) bullseye: resolved (fixed in 4.6.0+p1-0+deb11u1) forky: resolved (fixed in 5.0.0-1) sid: resolved (fixed in 5.0.0-1) trixie: resolved (fixed in 5.0.0-1)

CVE-2021-44718 [MEDIUM] CVE-2021-44718: wolfssl - wolfSSL through 5.0.0 allows an attacker to cause a denial of service and infini... wolfSSL through 5.0.0 allows an attacker to cause a denial of service and infinite loop in the client component by sending crafted traffic from a Machine-in-the-Middle (MITM) position. The root cause is that the client module accepts TLS messages that normally are only sent to TLS servers. Scope: local bookworm: resolved (fixed in 5.1.1-1) bullseye: resolved (fixe

CVE-2020-36177 [CRITICAL] CVE-2020-36177: wolfssl - RsaPad_PSS in wolfcrypt/src/rsa.c in wolfSSL before 4.6.0 has an out-of-bounds w... 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. Scope: local bookworm: resolved (fixed in 4.6.0-1) bullseye: resolved (fixed in 4.6.0-1) forky: resolved (fixed in 4.6.0-1) sid: resolved (fixed in 4.6.0-1) trixie: resolved (fixed in 4.6.0-1)

CVE-2020-12457 [HIGH] CVE-2020-12457: wolfssl - An issue was discovered in wolfSSL before 4.5.0. It mishandles the change_cipher... 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. Scope: local bookworm: resolved (fixed in 4.5.0+dfsg-1) bull

CVE-2020-11713 [HIGH] CVE-2020-11713: wolfssl - wolfSSL 4.3.0 has mulmod code in wc_ecc_mulmod_ex in ecc.c that does not properl... wolfSSL 4.3.0 has mulmod code in wc_ecc_mulmod_ex in ecc.c that does not properly resist timing side-channel attacks. Scope: local bookworm: resolved (fixed in 4.4.0+dfsg-1) bullseye: resolved (fixed in 4.4.0+dfsg-1) forky: resolved (fixed in 4.4.0+dfsg-1) sid: resolved (fixed in 4.4.0+dfsg-1) trixie: resolved (fixed in 4.4.0+dfsg-1)

CVE-2020-15309 [HIGH] CVE-2020-15309: wolfssl - An issue was discovered in wolfSSL before 4.5.0, when single precision is not em... 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). Scope: local bookworm: resolved (fi

CVE-2020-24585 [MEDIUM] CVE-2020-24585: wolfssl - An issue was discovered in the DTLS handshake implementation in wolfSSL before 4... 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. Scope: local bookworm: resolved (fixed in 4.5.0+dfsg-1) bullseye: resolved (fixed in 4.5.0+dfsg-1) forky: resolved (fixed in 4.5.0+dfsg-1

CVE-2020-11735 [MEDIUM] CVE-2020-11735: wolfssl - The private-key operations in ecc.c in wolfSSL before 4.4.0 do not use a constan... 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." Scope: local bookworm: resolved (fixed in 4.4.0+dfsg-1) bullseye: resolved (fixed in 4.4.0+dfsg-1) forky: resolved (fixed in 4.4.0+dfsg-1) sid: resolved (fixed in 4.4.0+dfsg-1) trixie: resol

CVE-2020-24613 [MEDIUM] CVE-2020-24613: wolfssl - wolfSSL before 4.5.0 mishandles TLS 1.3 server data in the WAIT_CERT_CR state, w... 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 cl