简体中文

CVE-2024-5535：详情

CVE-2024-5535

9.1
/
严重
6.7%V4
2024-06-27
10h30 +00:00
Overflow
Network
2026-10-15
00h29 +00:00
CVE.org
NVD
指定 CVE 通知
随时了解指定 CVE 的变更。
管理通知

CVE 描述

SSL_select_next_proto buffer overread

Issue summary: Calling the OpenSSL API function SSL_select_next_proto with an empty supported client protocols buffer may cause a crash or memory contents to be sent to the peer. Impact summary: A buffer overread can have a range of potential consequences such as unexpected application beahviour or a crash. In particular this issue could result in up to 255 bytes of arbitrary private data from memory being sent to the peer leading to a loss of confidentiality. However, only applications that directly call the SSL_select_next_proto function with a 0 length list of supported client protocols are affected by this issue. This would normally never be a valid scenario and is typically not under attacker control but may occur by accident in the case of a configuration or programming error in the calling application. The OpenSSL API function SSL_select_next_proto is typically used by TLS applications that support ALPN (Application Layer Protocol Negotiation) or NPN (Next Protocol Negotiation). NPN is older, was never standardised and is deprecated in favour of ALPN. We believe that ALPN is significantly more widely deployed than NPN. The SSL_select_next_proto function accepts a list of protocols from the server and a list of protocols from the client and returns the first protocol that appears in the server list that also appears in the client list. In the case of no overlap between the two lists it returns the first item in the client list. In either case it will signal whether an overlap between the two lists was found. In the case where SSL_select_next_proto is called with a zero length client list it fails to notice this condition and returns the memory immediately following the client list pointer (and reports that there was no overlap in the lists). This function is typically called from a server side application callback for ALPN or a client side application callback for NPN. In the case of ALPN the list of protocols supplied by the client is guaranteed by libssl to never be zero in length. The list of server protocols comes from the application and should never normally be expected to be of zero length. In this case if the SSL_select_next_proto function has been called as expected (with the list supplied by the client passed in the client/client_len parameters), then the application will not be vulnerable to this issue. If the application has accidentally been configured with a zero length server list, and has accidentally passed that zero length server list in the client/client_len parameters, and has additionally failed to correctly handle a "no overlap" response (which would normally result in a handshake failure in ALPN) then it will be vulnerable to this problem. In the case of NPN, the protocol permits the client to opportunistically select a protocol when there is no overlap. OpenSSL returns the first client protocol in the no overlap case in support of this. The list of client protocols comes from the application and should never normally be expected to be of zero length. However if the SSL_select_next_proto function is accidentally called with a client_len of 0 then an invalid memory pointer will be returned instead. If the application uses this output as the opportunistic protocol then the loss of confidentiality will occur. This issue has been assessed as Low severity because applications are most likely to be vulnerable if they are using NPN instead of ALPN - but NPN is not widely used. It also requires an application configuration or programming error. Finally, this issue would not typically be under attacker control making active exploitation unlikely. The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue. Due to the low severity of this issue we are not issuing new releases of OpenSSL at this time. The fix will be included in the next releases when they become available.

CVE 信息

相关弱点

CWE-ID 弱点名称 来源
CWE-125 Out-of-bounds Read
The product reads data past the end, or before the beginning, of the intended buffer.

指标

指标 评分 严重程度 CVSS 向量 来源
V3.1 9.1 CRITICAL CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

Base: Exploitabilty Metrics

The Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component.

Attack Vector

This metric reflects the context by which vulnerability exploitation is possible.

Network

The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).

Attack Complexity

This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability.

Low

Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success when attacking the vulnerable component.

Privileges Required

This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.

None

The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.

User Interaction

This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable component.

None

The vulnerable system can be exploited without interaction from any user.

Base: Scope Metrics

The Scope metric captures whether a vulnerability in one vulnerable component impacts resources in components beyond its security scope.

Scope

Formally, a security authority is a mechanism (e.g., an application, an operating system, firmware, a sandbox environment) that defines and enforces access control in terms of how certain subjects/actors (e.g., human users, processes) can access certain restricted objects/resources (e.g., files, CPU, memory) in a controlled manner. All the subjects and objects under the jurisdiction of a single security authority are considered to be under one security scope. If a vulnerability in a vulnerable component can affect a component which is in a different security scope than the vulnerable component, a Scope change occurs. Intuitively, whenever the impact of a vulnerability breaches a security/trust boundary and impacts components outside the security scope in which vulnerable component resides, a Scope change occurs.

Unchanged

An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.

Base: Impact Metrics

The Impact metrics capture the effects of a successfully exploited vulnerability on the component that suffers the worst outcome that is most directly and predictably associated with the attack. Analysts should constrain impacts to a reasonable, final outcome which they are confident an attacker is able to achieve.

Confidentiality Impact

This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability.

High

There is a total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.

Integrity Impact

This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.

None

There is no loss of integrity within the impacted component.

Availability Impact

This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability.

High

There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Temporal Metrics

The Temporal metrics measure the current state of exploit techniques or code availability, the existence of any patches or workarounds, or the confidence in the description of a vulnerability.

Environmental Metrics

These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user’s organization, measured in terms of Confidentiality, Integrity, and Availability.

 134c704f-9b21-4f2e-91b3-4a467353bcc0

EPSS

EPSS 是一种预测漏洞被利用可能性的评分模型。

EPSS 评分

EPSS 模型生成一个介于 0 到 1（即 0% 到 100%）之间的概率评分。评分越高，漏洞被利用的可能性越大。

EPSS 百分位

百分位用于根据 EPSS 评分对 CVE 进行排名。例如，EPSS 百分位为第 95 的 CVE，其被利用的可能性高于 95% 的其他 CVE。因此，百分位可用于比较不同 CVE 的 EPSS 评分。
EPSS First.org

相关产品

配置 0

Openssl>>Openssl >> Version 从（含） 1.0.2 至（不含） 1.0.2zk

Openssl>>Openssl >> Version 从（含） 1.1.1 至（不含） 1.1.1za

Openssl>>Openssl >> Version 从（含） 3.0.0 至（不含） 3.0.15

Openssl>>Openssl >> Version 从（含） 3.1.0 至（不含） 3.1.7

Openssl>>Openssl >> Version 从（含） 3.2.0 至（不含） 3.2.3

Openssl>>Openssl >> Version 从（含） 3.3.0 至（不含） 3.3.2

配置 0

Debian>>Debian_linux >> Version 11.0

配置 0

Netapp>>Active_iq_unified_manager >> Version -

Netapp>>Active_iq_unified_manager >> Version -

Netapp>>Active_iq_unified_manager >> Version -

Netapp>>Management_services_for_element_software_and_netapp_hci >> Version -

Netapp>>Oncommand_insight >> Version -

Netapp>>Oncommand_workflow_automation >> Version -

Netapp>>Ontap_select_deploy_administration_utility >> Version -

Netapp>>Ontap_tools >> Version -

Netapp>>Snapcenter >> Version 至（不含） 6.0.1

Netapp>>Snapmanager >> Version -

配置 0

Netapp>>Bootstrap_os >> Version -

Netapp>>Hci_compute_node >> Version -

配置 0

Netapp>>A250_firmware >> Version -

Netapp>>A250 >> Version -

配置 0

Netapp>>500f_firmware >> Version -

Netapp>>500f >> Version -

配置 0

Netapp>>C250_firmware >> Version -

Netapp>>C250 >> Version -

配置 0

Netapp>>H300s_firmware >> Version -

Netapp>>H300s >> Version -

配置 0

Netapp>>H500s_firmware >> Version -

Netapp>>H500s >> Version -

配置 0

Netapp>>H700s_firmware >> Version -

Netapp>>H700s >> Version -

配置 0

Netapp>>H410s_firmware >> Version -

Netapp>>H410s >> Version -

配置 0

Netapp>>H410c_firmware >> Version -

Netapp>>H410c >> Version -

配置 0

Netapp>>H610c_firmware >> Version -

Netapp>>H610c >> Version -

配置 0

Netapp>>H610s_firmware >> Version -

Netapp>>H610s >> Version -

配置 0

Netapp>>H615c_firmware >> Version -

Netapp>>H615c >> Version -

配置 0

Siemens>>Simatic_s7-1500_tm_mfp_firmware >> Version 至（不含） 1.1.1

Siemens>>Simatic_s7-1500_tm_mfp >> Version -

配置 0

Siemens>>Sidis_prime >> Version 至（不含） 4.0.700

配置 0

Siemens>>Simatic_s7-1500_cpu_1518-4_pn\/dp_mfp_firmware >> Version 从（含） 3.1.0 至（不含） 3.1.5

Siemens>>Simatic_s7-1500_cpu_1518-4_pn\/dp_mfp >> Version -

配置 0

Siemens>>Scalance_wab762-1_firmware >> Version 至（不含） 3.0.0

Siemens>>Scalance_wab762-1 >> Version -

配置 0

Siemens>>Scalance_wam763-1_firmware >> Version 至（不含） 3.0.0

Siemens>>Scalance_wam763-1 >> Version -

配置 0

Siemens>>Scalance_wam766-1_firmware >> Version 至（不含） 3.0.0

Siemens>>Scalance_wam766-1 >> Version -

配置 0

Siemens>>Scalance_wub762-1_firmware >> Version 至（不含） 3.0.0

Siemens>>Scalance_wub762-1 >> Version -

配置 0

Siemens>>Scalance_wub762-1_ifeatures_firmware >> Version 至（不含） 3.0.0

Siemens>>Scalance_wub762-1_ifeatures >> Version -

配置 0

Siemens>>Scalance_wum763-1_firmware >> Version 至（不含） 3.0.0

Siemens>>Scalance_wum763-1 >> Version -

配置 0

Siemens>>Scalance_wum766-1_firmware >> Version 至（不含） 3.0.0

Siemens>>Scalance_wum766-1 >> Version -

配置 0

Siemens>>Sinec_ins >> Version 至（不含） 1.0

Siemens>>Sinec_ins >> Version 1.0

Siemens>>Sinec_ins >> Version 1.0

Siemens>>Sinec_ins >> Version 1.0

Siemens>>Sinec_ins >> Version 1.0

Siemens>>Sinec_ins >> Version 1.0

配置 0

Siemens>>Sinec_os >> Version 至（不含） 3.1

Siemens>>Ruggedcom_rst2428p >> Version -

Siemens>>Scalance_xch328 >> Version -

Siemens>>Scalance_xcm324 >> Version -

Siemens>>Scalance_xcm328 >> Version -

Siemens>>Scalance_xcm332 >> Version -

Siemens>>Scalance_xrh334 >> Version -

Siemens>>Scalance_xrm334 >> Version -

配置 0

Siemens>>Simatic_s7-1500_cpu_1518f-4_pn\/dp_mfp_firmware >> Version 从（含） 3.1.0 至（不含） 3.1.5

Siemens>>Simatic_s7-1500_cpu_1518f-4_pn\/dp_mfp >> Version -

配置 0

Siemens>>Siplus_s7-1500_cpu_1518-4_pn\/dp_mfp_firmware >> Version 从（含） 3.1.0 至（不含） 3.1.5

Siemens>>Siplus_s7-1500_cpu_1518-4_pn\/dp_mfp >> Version -

参考资料

http://www.openwall.com/lists/oss-security/2024/06/27/1
Tags : Mailing List, Third Party Advisory
http://www.openwall.com/lists/oss-security/2024/06/28/4
Tags : Mailing List, Third Party Advisory
http://www.openwall.com/lists/oss-security/2024/08/15/1
Tags : Mailing List, Third Party Advisory
cvefind.com 上展示的信息来源于多个精心选择的权威数据源。CVE 数据由 MITRE Corporation 和 National Vulnerability Database (NVD) 提供。已知被利用漏洞（KEV）目录来源于 Cybersecurity and Infrastructure Security Agency (CISA)，EPSS 评分来自 FIRST.org。此外，软件弱点（CWE）和常见攻击模式（CAPEC）数据由 MITRE Corporation 维护，硬件和软件配置（CPE）信息由 NVD 提供。