CVE-2023-6937
published 2024-02-15CVE-2023-6937: 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…
PriorityP427medium5.3CVSS 3.1
AVNACLPRNUINSUCLINAN
EPSS
0.51%
40.7th percentile
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
10 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | wolfssl | < wolfssl 5.6.6-1.2 (forky) | wolfssl 5.6.6-1.2 (forky) |
| msrc | azl3_mariadb_10.11.6-3_on_azure_linux_3.0 | — | — |
| msrc | azure_linux_3.0_arm | — | — |
| msrc | azure_linux_3.0_x64 | — | — |
| msrc | cbl_mariner_2.0_arm | — | — |
| msrc | cbl_mariner_2.0_x64 | — | — |
| wolfssl | wolfssl | < 5.6.6 | 5.6.6 |
| wolfssl | wolfssl | <= 5.6.4 | — |
| wolfssl | wolfssl | >= 0 < 5.6.6-1.2 | 5.6.6-1.2 |
| wolfssl | wolfssl | >= 0 < 5.6.6-1.2 | 5.6.6-1.2 |
CVSS provenance
nvdv3.15.3MEDIUMCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
osv5.3MEDIUM
vendor_debian5.3MEDIUM
vendor_msrc5.3MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Microsoft
Improper (D)TLS key boundary enforcement
vendor_msrc·2024-02-13·CVSS 5.3
CVE-2023-6937 [MEDIUM] CWE-20 Improper (D)TLS key boundary enforcement
Improper (D)TLS key boundary enforcement
FAQ: Is Azure Linux the only Microsoft product that includes this open-source library and is therefore potentially affected by this vulnerability?
One of the main benefits to our customers who choose to use the Azure Linux distro is the commitment to keep it up to date with the most recent and most secure versions of the open source libraries with which the distro is composed. Microsoft is committed to transparency in this work which is why we began publishing CSAF/VEX in October 2025. See this blog post for more information. If impact to additional products is identified, we will update the CVE to reflect this.
Mariner: Mariner
wolfSSL: wolfSSL
Customer Action Required: Yes
Remediation: CBL-Mariner Releases
Reference: https://learn.microsoft.
Debian
CVE-2023-6937: wolfssl - wolfSSL prior to 5.6.6 did not check that messages in one (D)TLS record do not s...
vendor_debian·2023·CVSS 5.3
CVE-2023-6937 [MEDIUM] CVE-2023-6937: wolfssl - wolfSSL prior to 5.6.6 did not check that messages in one (D)TLS record do not s...
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.
Scope: local
bookworm: open
bullseye: open
forky: resolved (fixed in 5.6.6-1.2)
sid: resolved (fixed in 5.6.6-1.2)
tri
GHSA
GHSA-ff3x-q8pg-rh37: wolfSSL prior to 5
ghsa_unreviewed·2024-02-15
CVE-2023-6937 [MEDIUM] CWE-20 GHSA-ff3x-q8pg-rh37: wolfSSL prior to 5
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.
OSV
CVE-2023-6937: wolfSSL prior to 5
osv·2024-02-15·CVSS 5.3
CVE-2023-6937 [MEDIUM] CVE-2023-6937: wolfSSL prior to 5
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.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2024-02-15
Published