Improper (D)TLS key boundary enforcement
Published Feb 15, 2024
5.3
MEDIUMCVSS 3.1
EPSS 0.51%
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
-
- Version 0StatusaffectedConstraints<=5.6.4
- Version
-
- Version 0StatusaffectedConstraints<=5.64
- Version
No Red Hat product state for this CVE.
No package ranges for this CVE.
Remediation
Vendor solution
The fix for this issue is located in the following GitHub Pull Request: https://github.com/wolfSSL/wolfssl/pull/7029 https://github.com/wolfSSL/wolfssl/pull/7029 .
References (3)
- https://euvd.enisa.europa.eu/vulnerability/EUVD-2023-59135 Advisory
- https://github.com/wolfSSL/wolfssl/pull/7029 patchIssue Tracking
- https://www.wolfssl.com/docs/security-vulnerabilities/ vendor-advisoryVendor Advisory
| Link | Providers | Tags |
|---|---|---|
| https://euvd.enisa.europa.eu/vulnerability/EUVD-2023-59135 | Advisory | |
| https://github.com/wolfSSL/wolfssl/pull/7029 | patchIssue Tracking | |
| https://www.wolfssl.com/docs/security-vulnerabilities/ | vendor-advisoryVendor Advisory |
Change history (0)
No recorded changes yet.