CVE-2024-4741

/// Technical description

Issue summary: Calling the OpenSSL API function SSL_free_buffers may cause

memory to be accessed that was previously freed in some situations

Impact summary: A use after free can have a range of potential consequences such

as the corruption of valid data, crashes or execution of arbitrary code.

However, only applications that directly call the SSL_free_buffers function are

affected by this issue. Applications that do not call this function are not

vulnerable. Our investigations indicate that this function is rarely used by

applications.

The SSL_free_buffers function is used to free the internal OpenSSL buffer used

when processing an incoming record from the network. The call is only expected

to succeed if the buffer is not currently in use. However, two scenarios have

been identified where the buffer is freed even when still in use.

The first scenario occurs where a record header has been received from the

network and processed by OpenSSL, but the full record body has not yet arrive

/// Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

/// References