Executive Summary

Informations
Name CVE-2023-6937 First vendor Publication 2024-02-15
Vendor Cve Last vendor Modification 2025-02-21

Security-Database Scoring CVSS v3

Cvss vector : CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Overall CVSS Score 5.3
Base Score 5.3 Environmental Score 5.3
impact SubScore 1.4 Temporal Score 5.3
Exploitabality Sub Score 3.9
 
Attack Vector Network Attack Complexity Low
Privileges Required None User Interaction None
Scope Unchanged Confidentiality Impact Low
Integrity Impact None Availability Impact None
Calculate full CVSS 3.0 Vectors scores

Security-Database Scoring CVSS v2

Cvss vector :
Cvss Base Score N/A Attack Range N/A
Cvss Impact Score N/A Attack Complexity N/A
Cvss Expoit Score N/A Authentication N/A
Calculate full CVSS 2.0 Vectors scores

Detail

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.

Original Source

Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-6937

CPE : Common Platform Enumeration

TypeDescriptionCount
Application 5

Sources (Detail)

https://github.com/wolfSSL/wolfssl/pull/7029
https://www.wolfssl.com/docs/security-vulnerabilities/
Source Url

Alert History

If you want to see full details history, please login or register.
0
1
2
3
Date Informations
2025-02-21 21:20:56
  • Multiple Updates
2024-11-25 05:25:08
  • Multiple Updates
2024-02-16 05:27:25
  • Multiple Updates
2024-02-15 21:27:25
  • First insertion