CVE-2023-6937
low-risk
Published 2024-02-15
wolfSSL prior to 5.6.6 did not check that messages in one (D)TLS record do not span key boundaries. As a result, it was possible to combine (D)TLS messages using different keys into one (D)TLS record. The most extreme edge case is that, in (D)TLS 1.3, it was possible that an unencrypted (D)TLS 1.3 record from the server containing first a ServerHello message and then the rest of the first server flight would be accepted by a wolfSSL client. In (D)TLS 1.3 the handshake is encrypted after the ServerHello but a wolfSSL client would accept an unencrypted flight from the server. This does not compromise key negotiation and authentication so it is assigned a low severity rating.
Do I need to act?
-
0.44% chance of exploitation
EPSS score — low exploit probability
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
5
CVSS 5.3/10
Medium
NETWORK
/ LOW complexity
Affected Products (1)
Affected Vendors
References (4)
Issue Tracking
https://github.com/wolfSSL/wolfssl/pull/7029
Vendor Advisory
https://www.wolfssl.com/docs/security-vulnerabilities/
Issue Tracking
https://github.com/wolfSSL/wolfssl/pull/7029
Vendor Advisory
https://www.wolfssl.com/docs/security-vulnerabilities/
28
/ 100
low-risk
Severity
21/34 · High
Exploitability
2/34 · Minimal
Exposure
5/34 · Minimal