Compliance Impact

The provided information does not specify any direct impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.

Useful 0 Not Useful 0

Executive Summary

This vulnerability involves a flaw in the TLS OCSP stapling feature where a malicious server can send a specially crafted OCSP response through the status_request extension. This crafted response triggers a double-free error in the client's certificate verification process.

A double-free occurs when the same memory is freed twice, which can corrupt the heap memory and cause unpredictable behavior in the client application.

Useful 0 Not Useful 0

Impact Analysis

If successfully exploited, this vulnerability can corrupt heap memory in the TLS client, potentially leading to a Denial of Service (DoS) where the client application crashes or becomes unresponsive.

In some cases, it might allow an attacker to execute arbitrary code or cause other undefined behaviors, although achieving reliable code execution is complex and depends heavily on the environment.

Since OCSP stapling is not enabled by default, the risk is limited to clients that have this feature enabled and connect to a malicious server.

Useful 0 Not Useful 0

Mitigation Strategies

To mitigate this vulnerability, ensure that OCSP stapling is disabled if it is not required, as it is not enabled by default.

Avoid connecting TLS clients to untrusted or potentially malicious servers that could deliver crafted OCSP stapled responses.

Monitor for updates or patches from OpenSSL and apply them promptly once available to address this double-free issue.

Useful 0 Not Useful 0