CVE-2020-1971 : Detail

CVE-2020-1971

5.9
/
Medium
Memory Corruption
1.35%V3
Network
2020-12-08
15h30 +00:00
2024-09-17
02h57 +00:00
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

EDIPARTYNAME NULL pointer dereference

The X.509 GeneralName type is a generic type for representing different types of names. One of those name types is known as EDIPartyName. OpenSSL provides a function GENERAL_NAME_cmp which compares different instances of a GENERAL_NAME to see if they are equal or not. This function behaves incorrectly when both GENERAL_NAMEs contain an EDIPARTYNAME. A NULL pointer dereference and a crash may occur leading to a possible denial of service attack. OpenSSL itself uses the GENERAL_NAME_cmp function for two purposes: 1) Comparing CRL distribution point names between an available CRL and a CRL distribution point embedded in an X509 certificate 2) When verifying that a timestamp response token signer matches the timestamp authority name (exposed via the API functions TS_RESP_verify_response and TS_RESP_verify_token) If an attacker can control both items being compared then that attacker could trigger a crash. For example if the attacker can trick a client or server into checking a malicious certificate against a malicious CRL then this may occur. Note that some applications automatically download CRLs based on a URL embedded in a certificate. This checking happens prior to the signatures on the certificate and CRL being verified. OpenSSL's s_server, s_client and verify tools have support for the "-crl_download" option which implements automatic CRL downloading and this attack has been demonstrated to work against those tools. Note that an unrelated bug means that affected versions of OpenSSL cannot parse or construct correct encodings of EDIPARTYNAME. However it is possible to construct a malformed EDIPARTYNAME that OpenSSL's parser will accept and hence trigger this attack. All OpenSSL 1.1.1 and 1.0.2 versions are affected by this issue. Other OpenSSL releases are out of support and have not been checked. Fixed in OpenSSL 1.1.1i (Affected 1.1.1-1.1.1h). Fixed in OpenSSL 1.0.2x (Affected 1.0.2-1.0.2w).

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE-476 NULL Pointer Dereference
The product dereferences a pointer that it expects to be valid but is NULL.

Metrics

Metrics Score Severity CVSS Vector Source
V3.1 5.9 MEDIUM CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/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.

High

successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected.

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.

None

There is no loss of confidentiality within the impacted component.

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.

[email protected]
V2 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P [email protected]

EPSS

EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.

EPSS Score

The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.

EPSS Percentile

The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.

Products Mentioned

Configuraton 0

Openssl>>Openssl >> Version From (including) 1.0.2 To (excluding) 1.0.2x

Openssl>>Openssl >> Version From (including) 1.1.1 To (excluding) 1.1.1i

Configuraton 0

Debian>>Debian_linux >> Version 9.0

Debian>>Debian_linux >> Version 10.0

Configuraton 0

Fedoraproject>>Fedora >> Version 32

Fedoraproject>>Fedora >> Version 33

Configuraton 0

Oracle>>Api_gateway >> Version 11.1.2.4.0

Oracle>>Business_intelligence >> Version 5.5.0.0.0

Oracle>>Business_intelligence >> Version 5.9.0.0.0

Oracle>>Business_intelligence >> Version 12.2.1.3.0

Oracle>>Business_intelligence >> Version 12.2.1.4.0

Oracle>>Communications_cloud_native_core_network_function_cloud_native_environment >> Version 1.10.0

  • Oracle>>Communications_cloud_native_core_network_function_cloud_native_environment >> Version 1.10.0 (Open CPE detail)

Oracle>>Communications_diameter_intelligence_hub >> Version From (including) 8.0.0 To (including) 8.1.0

Oracle>>Communications_diameter_intelligence_hub >> Version From (including) 8.2.0 To (including) 8.2.3

Oracle>>Communications_session_border_controller >> Version cz8.2

Oracle>>Communications_session_border_controller >> Version cz8.3

Oracle>>Communications_session_border_controller >> Version cz8.4

Oracle>>Communications_session_router >> Version cz8.2

Oracle>>Communications_session_router >> Version cz8.3

Oracle>>Communications_session_router >> Version cz8.4

Oracle>>Communications_subscriber-aware_load_balancer >> Version cz8.2

Oracle>>Communications_subscriber-aware_load_balancer >> Version cz8.3

Oracle>>Communications_subscriber-aware_load_balancer >> Version cz8.4

Oracle>>Communications_unified_session_manager >> Version scz8.2.5

Oracle>>Enterprise_communications_broker >> Version pcz3.1

Oracle>>Enterprise_communications_broker >> Version pcz3.2

Oracle>>Enterprise_communications_broker >> Version pcz3.3

Oracle>>Enterprise_manager_base_platform >> Version 13.3.0.0

Oracle>>Enterprise_manager_base_platform >> Version 13.4.0.0

Oracle>>Enterprise_manager_for_storage_management >> Version 13.4.0.0

Oracle>>Enterprise_manager_ops_center >> Version 12.4.0.0

Oracle>>Enterprise_session_border_controller >> Version cz8.2

Oracle>>Enterprise_session_border_controller >> Version cz8.3

Oracle>>Enterprise_session_border_controller >> Version cz8.4

Oracle>>Essbase >> Version 21.2

Oracle>>Graalvm >> Version 19.3.4

Oracle>>Graalvm >> Version 20.3.0

Oracle>>Http_server >> Version 12.2.1.4.0

Oracle>>Jd_edwards_enterpriseone_tools >> Version To (excluding) 9.2.5.3

Oracle>>Jd_edwards_world_security >> Version a9.4

Oracle>>Mysql >> Version To (including) 8.0.22

Oracle>>Mysql_server >> Version To (including) 5.7.32

Oracle>>Mysql_server >> Version From (including) 8.0.15 To (including) 8.0.22

Oracle>>Peoplesoft_enterprise_peopletools >> Version 8.56

Oracle>>Peoplesoft_enterprise_peopletools >> Version 8.57

Oracle>>Peoplesoft_enterprise_peopletools >> Version 8.58

Configuraton 0

Netapp>>Active_iq_unified_manager >> Version -

Netapp>>Active_iq_unified_manager >> Version -

Netapp>>Clustered_data_ontap_antivirus_connector >> Version -

Netapp>>Data_ontap >> Version -

Netapp>>E-series_santricity_os_controller >> Version From (including) 11.0.0 To (including) 11.60.3

Netapp>>Hci_management_node >> Version -

Netapp>>Manageability_software_development_kit >> Version -

Netapp>>Oncommand_insight >> Version -

Netapp>>Oncommand_workflow_automation >> Version -

Netapp>>Plug-in_for_symantec_netbackup >> Version -

Netapp>>Santricity_smi-s_provider >> Version -

Netapp>>Snapcenter >> Version -

Netapp>>Solidfire >> Version -

Netapp>>Hci_compute_node >> Version -

Netapp>>Hci_storage_node >> Version -

Configuraton 0

Netapp>>Ef600a_firmware >> Version -

Netapp>>Ef600a >> Version -

Configuraton 0

Netapp>>Aff_a250_firmware >> Version -

Netapp>>Aff_a250 >> Version -

Configuraton 0

Tenable>>Log_correlation_engine >> Version To (excluding) 6.0.9

Tenable>>Nessus_network_monitor >> Version To (excluding) 5.13.1

Configuraton 0

Siemens>>Sinec_infrastructure_network_services >> Version To (excluding) 1.0.1.1

Configuraton 0

Nodejs>>Node.js >> Version From (including) 10.0.0 To (including) 10.12.0

Nodejs>>Node.js >> Version From (including) 10.13.0 To (excluding) 10.23.1

Nodejs>>Node.js >> Version From (including) 12.0.0 To (including) 12.12.0

Nodejs>>Node.js >> Version From (including) 12.13.0 To (excluding) 12.20.1

Nodejs>>Node.js >> Version From (including) 14.0.0 To (including) 14.14.0

Nodejs>>Node.js >> Version From (including) 14.15.0 To (excluding) 14.15.4

Nodejs>>Node.js >> Version From (including) 15.0.0 To (excluding) 15.5.0

References