CVE-2023-3724: critical vulnerability in wolfSSL
TLS 1.3 client issue handling malicious server when not including a KSE and PSK extension
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
28Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 9.1epss 0.7%
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.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Affected products
wolfSSL · wolfSSLRelated CVEs — wolfSSL
In the same product, most dangerous first.
CVE-2017-13099HIGHwolfSSL Bleichenbacher/ROBOTEPSS 27.4%CVE-2017-2800HIGHCVE-2017-2800EPSS 8.5%CVE-2024-0901HIGHSEGV and out of bounds memory read from malicious packetEPSS 0.7%CVE-2023-6936MEDIUM Heap-buffer over-read with WOLFSSL_CALLBACKSEPSS 0.6%CVE-2026-5194CRITICALwolfSSL ECDSA Certificate VerificationEPSS 0.6%CVE-2024-5991CRITICALBuffer overread in domain name matchingEPSS 0.6%