CVE-2022-38153: Medium severity wolfSSL wolfssl vulnerability
An issue was discovered in wolfSSL before 5.5.0 (when --enable-session-ticket is used); however, only version 5.3.0 is exploitable. Man-in-the-middle attackers or a malicious server can crash TLS 1.2 clients during a handshake. If an attacker injects a large ticket (more than 256 bytes) into a NewSessionTicket message in a TLS 1.2 handshake, and the client has a non-empty session cache, the session cache frees a pointer that points to unallocated memory, causing the client to crash with a "free(): invalid pointer" message. NOTE: It is likely that this is also exploitable during TLS 1.3 handshakes between a client and a malicious server. With TLS 1.3, it is not possible to exploit this as a man-in-the-middle.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/wolfsslto a version that resolves this vulnerability.Fixed in 5.5.4-2+deb12u2Fixed in 5.5.4-2+deb12u3Fixed in 5.7.2-0.1+deb13u2Fixed in 5.9.2-1.2 - Upgrade
Upgrade
debian/wolfsslto a version that resolves this vulnerability.Fixed in 5.5.3-1 - Upgrade
Upgrade
wolfSSLto a version that resolves this vulnerability.Fixed in 5.5.0
Event History
Frequently Asked Questions
What is the vulnerability ID of this issue in wolfSSL?
The vulnerability ID is CVE-2022-38153.
What is the severity rating of CVE-2022-38153?
The severity rating of CVE-2022-38153 is medium.
How does CVE-2022-38153 affect wolfSSL?
CVE-2022-38153 allows man-in-the-middle attackers or a malicious server to crash TLS 1.2 clients during a handshake in wolfSSL versions before 5.5.0 when '--enable-session-ticket' is used.
How can this vulnerability be exploited?
This vulnerability can be exploited by injecting a large ticket (more than 256 bytes) into a NewSessionTicket message during the TLS handshake.
Is there a fix available for CVE-2022-38153 in wolfSSL?
Yes, the fix for CVE-2022-38153 is included in wolfSSL version 5.5.0.