CVE-2021-3711
14h50 +00:00
Deskripsi CVE
SM2 Decryption Buffer Overflow
In order to decrypt SM2 encrypted data an application is expected to call the API function EVP_PKEY_decrypt(). Typically an application will call this function twice. The first time, on entry, the "out" parameter can be NULL and, on exit, the "outlen" parameter is populated with the buffer size required to hold the decrypted plaintext. The application can then allocate a sufficiently sized buffer and call EVP_PKEY_decrypt() again, but this time passing a non-NULL value for the "out" parameter. A bug in the implementation of the SM2 decryption code means that the calculation of the buffer size required to hold the plaintext returned by the first call to EVP_PKEY_decrypt() can be smaller than the actual size required by the second call. This can lead to a buffer overflow when EVP_PKEY_decrypt() is called by the application a second time with a buffer that is too small. A malicious attacker who is able present SM2 content for decryption to an application could cause attacker chosen data to overflow the buffer by up to a maximum of 62 bytes altering the contents of other data held after the buffer, possibly changing application behaviour or causing the application to crash. The location of the buffer is application dependent but is typically heap allocated. Fixed in OpenSSL 1.1.1l (Affected 1.1.1-1.1.1k).Informasi CVE
Kelemahan Terkait
| Nama Kelemahan | Sumber | |
|---|---|---|
| Buffer Copy without Checking Size of Input The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer. |
Metrik
| Metrik | Skor | Tingkat keparahan | CVSS Vektor | Sumber |
|---|---|---|---|---|
| V3.1 | 9.8 | CRITICAL |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Informasi lebih lanjut
Base: Exploitabilty MetricsThe 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 MetricsThe 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 MetricsThe 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. High There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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 MetricsThe 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 MetricsThese 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. |
nvd@nist.gov |
| V2 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P | nvd@nist.gov |
EPSS
Skor EPSS
Persentil EPSS
Produk yang Disebutkan
Konfigurasi 0
Openssl>>Openssl >> Version Dari (termasuk) 1.1.1 Hingga (tidak termasuk) 1.1.1l
Konfigurasi 0
Debian>>Debian_linux >> Version 10.0
Debian>>Debian_linux >> Version 11.0
Konfigurasi 0
Netapp>>Active_iq_unified_manager >> Version -
Netapp>>Active_iq_unified_manager >> Version -
Netapp>>Clustered_data_ontap >> Version -
Netapp>>Clustered_data_ontap_antivirus_connector >> Version -
Netapp>>E-series_santricity_os_controller >> Version Dari (termasuk) 11.0 Hingga (termasuk) 11.50.2
Netapp>>Hci_management_node >> Version -
Netapp>>Manageability_software_development_kit >> Version -
Netapp>>Oncommand_insight >> Version -
Netapp>>Oncommand_workflow_automation >> Version -
Netapp>>Santricity_smi-s_provider >> Version -
Netapp>>Snapcenter >> Version -
Netapp>>Solidfire >> Version -
Netapp>>Storage_encryption >> Version -
Konfigurasi 0
Oracle>>Communications_cloud_native_core_security_edge_protection_proxy >> Version 1.7.0
Oracle>>Communications_cloud_native_core_unified_data_repository >> Version 1.15.0
Oracle>>Communications_session_border_controller >> Version 8.4
Oracle>>Communications_session_border_controller >> Version 9.0
Oracle>>Communications_unified_session_manager >> Version 8.2.5
Oracle>>Communications_unified_session_manager >> Version 8.4.5
Oracle>>Enterprise_communications_broker >> Version 3.2.0
Oracle>>Enterprise_communications_broker >> Version 3.3.0
Oracle>>Enterprise_session_border_controller >> Version 8.4
Oracle>>Enterprise_session_border_controller >> Version 9.0
Oracle>>Essbase >> Version Hingga (tidak termasuk) 11.1.2.4.47
Oracle>>Essbase >> Version Dari (termasuk) 21.1 Hingga (tidak termasuk) 21.3
Oracle>>Health_sciences_inform_publisher >> Version 6.2.1.1
Oracle>>Health_sciences_inform_publisher >> Version 6.3.1.1
Oracle>>Jd_edwards_enterpriseone_tools >> Version Hingga (tidak termasuk) 9.2.6.3
Oracle>>Jd_edwards_world_security >> Version a9.4
Oracle>>Mysql_connectors >> Version Hingga (termasuk) 8.0.27
Oracle>>Mysql_enterprise_monitor >> Version Hingga (termasuk) 8.0.25
Oracle>>Mysql_server >> Version Dari (termasuk) 5.7.0 Hingga (termasuk) 5.7.35
Oracle>>Mysql_server >> Version Dari (termasuk) 8.0.0 Hingga (termasuk) 8.0.26
Oracle>>Peoplesoft_enterprise_peopletools >> Version 8.57
Oracle>>Peoplesoft_enterprise_peopletools >> Version 8.58
Oracle>>Peoplesoft_enterprise_peopletools >> Version 8.59
Oracle>>Zfs_storage_appliance_kit >> Version 8.8
Konfigurasi 0
Tenable>>Nessus_network_monitor >> Version Hingga (termasuk) 5.13.1
Tenable>>Tenable.sc >> Version Dari (termasuk) 5.16.0 Hingga (termasuk) 5.19.1
Referensi
Tags : mailing-list
