A flaw was found in OpenSSL. Affected versions of this package are vulnerable to Information Exposure through the SSL_select_next_proto function. This flaw allows an attacker to cause unexpected application behavior or a crash by exploiting the buffer overread condition when the function is called with a zero-length client list. This issue is only exploitable if the application is misconfigured to use a zero-length server list and mishandles the 'no overlap' response in ALPN or uses the output as the opportunistic protocol in NPN.
Successful exploitation of this vulnerability could lead to the disclosure of sensitive information or Denial of Service (DoS). Specifically, it could result in a loss of confidentiality as up to 255 bytes of arbitrary private data from memory could be sent to the peer.
Successful exploitation of this vulnerability could lead to disclosure of sensitive information or Denial of Service (DoS). Specifically, Loss of confidentiality as up to 255 bytes of arbitrary private data from memory could be sent to the peer.
The vulnerability CVE-2024-5535 has been assessed as Low severity by OpenSSL. This is because the issue arises only when the SSL_select_next_proto function is called with an empty supported client protocols buffer, which is not a common scenario. The function is typically used in applications supporting ALPN or NPN, but the conditions required for the vulnerability to be exploited are rare and usually result from configuration or programming errors.
CVE-2024-5535
RedHat: 5.9 Medium
Netwitness: None
After a thorough analysis, we have determined that NetWitness is not impacted by this vulnerability as we do not use the vulnerable functions in our product or solutions.
NetWitness version 12.4.0.0 and later include both OpenSSL-3 and OpenSSL 1.1.1k. The NetWitness services utilize OpenSSL-3 (SafeLogic), which is FIPS compliant and not vulnerable. OpenSSL 1.1.1k serves as the system’s default OpenSSL, configured for the operating system’s operations.
Considering the context of OpenSSL 1.1.1k, NetWitness does not directly call the vulnerable function, and no misconfigurations were found related to the mentioned function. The vulnerability affects only applications that directly call the SSL_select_next_proto function with a 0 length list of supported client protocols. In NetWitness, HTTP/1.1 is used, which does not require ALPN or NPN for protocol negotiation. Hence, neither NPN nor ALPN is configured, which is another factor for the server not being vulnerable.
We are aware of third-party modules in NetWitness built using OpenSSL 1.1.1k. However, the possibility of exploitation is limited to configuration or programming errors within the specific library or module. Such scenarios are typically not under attacker control and would generally occur only by accident.
For both NetWitness and the third-party modules, an exploitation scenario would require an attacker to have full control over the machine and make necessary misconfigurations. This is highly complex and impractical. For example, exploiting this vulnerability via nginx in NetWitness would require an attacker to gain higher privileges to make configuration changes, which is unlikely.
The potential for exploitation of this vulnerability is limited. For an attacker to exploit this vulnerability, they would need to:
Given these conditions, active exploitation is unlikely. The vulnerability is more theoretical and would require a combination of multiple exploits and tactics, making the exploitation process highly complex and impractical.
The level of risk incurred by this vulnerability is minimal for NetWitness. Since NetWitness does not use the vulnerable function and does not configure ALPN or NPN, the risk is negligible. Even for third-party modules using OpenSSL 1.1.1k, the risk remains low due to the complexity required for exploitation. The primary risk would be a loss of confidentiality if an attacker could exploit the vulnerability, but this scenario is highly unlikely.
Overall, the impact on NetWitness is minimal, and the product is not affected by this vulnerability.
All currently supported NetWitness versions have the vulnerable library installed: 12.2.0.0, 12.2.0.1, 12.3.0.0, 12.3.1.0, 12.4.0.0, 12.4.1.0, 12.4.2.0
NetWitness Platform 12.3.1.0 and Earlier:
NetWitness Platform 12.4 and Later:
Netwitness has a defined End of Primary Support policy associated with all major versions. Please refer to the Product Version Life Cycle for additional details.
Read and use the information in this RSA Security Advisory to assist in avoiding any situation that might arise from the problems described herein. If you have any questions regarding this advisory, contact NetWitness Customer Support. RSA Security LLC and its affiliates distribute RSA Security Advisories in order to bring to the attention of users of the affected RSA products, important security information.
RSA recommends that all users determine the applicability of this information to their individual situations and take appropriate action. The information set forth herein is provided "as is" without a warranty of any kind. RSA disclaims all warranties, either express or implied, including the warranties of merchantability, fitness for a particular purpose, title and non-infringement.
In no event shall RSA, its affiliates or its suppliers, be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if RSA, its affiliates or its suppliers have been advised of the possibility of such damages. Some jurisdictions do not allow the exclusion or limitation of liability for consequential or incidental damages, so the foregoing limitation may not apply.