Search for packages
| purl | pkg:conan/wolfssl@4.7.1 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-3774-6bd4-8qcs
Aliases: CVE-2021-44718 |
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. |
Affected by 8 other vulnerabilities. |
|
VCID-6n4g-us9a-53g4
Aliases: CVE-2022-38152 |
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 WOLFSSL) by calling wolfSSL_clear(WOLFSSL* ssl) on it, the next received Client Hello (that resumes the previous session) crashes the server. Note that this bug is only triggered when resuming sessions using TLS session resumption. Only servers that use wolfSSL_clear instead of the recommended SSL_free; SSL_new sequence are affected. Furthermore, wolfSSL_clear is part of wolfSSL's compatibility layer and is not enabled by default. It is not part of wolfSSL's native API. |
Affected by 2 other vulnerabilities. |
|
VCID-av4q-73pk-tucd
Aliases: CVE-2022-25640 |
Improper Authentication 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. |
Affected by 6 other vulnerabilities. |
|
VCID-cum2-vp1j-syfc
Aliases: CVE-2022-34293 |
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. |
Affected by 5 other vulnerabilities. |
|
VCID-h2vp-p7fd-7bev
Aliases: CVE-2021-37155 |
Improper Handling of Exceptional Conditions wolfSSL does not produce a failure outcome when the serial number in an OCSP request differs from the serial number in the OCSP response. |
Affected by 9 other vulnerabilities. |
|
VCID-hguq-mr6k-jqd3
Aliases: CVE-2023-3724 |
Improper Certificate Validation If a TLS 1.3 client gets neither a PSK (pre shared key) extension nor a KSE (key share extension) when connecting to a malicious server, a default predictable buffer gets used for the IKM (Input Keying Material) value when generating the session master secret. Using a potentially known IKM value when generating the session master secret key compromises the key generated, allowing an eavesdropper to reconstruct it and potentially allowing access to or meddling with message contents in the session. This issue does not affect client validation of connected servers, nor expose private key information, but could result in an insecure TLS 1.3 session when not controlling both sides of the connection. wolfSSL recommends that TLS 1.3 client side users update the version of wolfSSL used. |
Affected by 0 other vulnerabilities. |
|
VCID-kksg-tc63-23bm
Aliases: CVE-2022-39173 |
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, two Client Hellos have to be sent: one in the resumed session, and a second one as a response to a Hello Retry Request message. |
Affected by 2 other vulnerabilities. |
|
VCID-mtcu-yhz9-c7b8
Aliases: CVE-2022-25638 |
Improper Certificate Validation 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. |
Affected by 6 other vulnerabilities. |
|
VCID-ubye-e3yx-pfbb
Aliases: CVE-2022-42905 |
In wolfSSL before 5.5.2, if callback functions are enabled (via the WOLFSSL_CALLBACKS flag), then a malicious TLS 1.3 client or network attacker can trigger a buffer over-read on the heap of 5 bytes. (WOLFSSL_CALLBACKS is only intended for debugging.) |
Affected by 0 other vulnerabilities. |
|
VCID-x4tg-m9be-2yfe
Aliases: CVE-2022-42961 |
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, WOLFSSL_CHECK_SIG_FAULTS can be used to address the vulnerability.) |
Affected by 0 other vulnerabilities. Affected by 2 other vulnerabilities. |
|
VCID-yyy6-k4y2-s3ep
Aliases: CVE-2021-38597 |
Insufficient Verification of Data Authenticity wolfSSL incorrectly skips OCSP verification in certain situations of irrelevant response data that contains the NoCheck extension. |
Affected by 9 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| This package is not known to fix vulnerabilities. | ||