CVE-2023-6937: Improper (D)TLS key boundary enforcement

Severity: medium (CVSS 5.3 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.5% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2024-02-15 · updated 2026-06-17
Weakness: CWE-20

Description

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.

Affected products

wolfSSL: before 5.6.6 — fixed in 5.6.6

How to fix

Upgrade to a fixed version: wolfSSL 5.6.6. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2023-6937 or the next vulnerability affects your stack