CVE-2020-1971: EDIPARTYNAME NULL pointer dereference
A null pointer dereference flaw was found in openssl. A remote attacker, able to control the arguments of the GENERALNAMEcmp function, could cause the application, compiled with openssl to crash resulting in a denial of service. The highest threat from this vulnerability is to system availability.
Other sources
As per upstream advisory:
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 GENERALNAMEcmp which compares different instances of a GENERALNAME to see if they are equal or not. This function behaves incorrectly when both GENERALNAMEs contain an EDIPARTYNAME. A NULL pointer dereference and a crash may occur leading to a possible denial of service attack.
OpenSSL itself uses the GENERALNAMEcmp 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 TSRESPverifyresponse and TSRESPverifytoken)
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 sserver, sclient and verify tools have support for the "-crldownload" option which implements automatic CRL downloading and this attack has been demonstrated to work against those tools.
— Red Hat
In GENERALNAMEcmp of v3genn.c , there is a possible denial of service due to a missing null check. This could lead to remote denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.
— OSV
OpenSSL - EDIPARTYNAME NULL pointer de-reference - This is a vulnerability in OpenSSL which may be exploited through Node.js. You can read more about it in https://www.openssl.org/news/secadv/20201208.txt
— Node.Js
OpenSSL is vulnerable to a denial of service, caused by a NULL pointer dereference. If the GENERALNAMEcmp function contain an EDIPARTYNAME, an attacker could exploit this vulnerability to cause the application to crash.
— IBM
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 GENERALNAMEcmp which compares different instances of a GENERALNAME to see if they are equal or not. This function behaves incorrectly when both GENERALNAMEs contain an EDIPARTYNAME. A NULL pointer dereference and a crash may occur leading to a possible denial of service attack. OpenSSL itself uses the GENERALNAMEcmp 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 TSRESPverifyresponse and TSRESPverifytoken) 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 sserver, sclient and verify tools have support for the "-crldownload" 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).
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
redhat/jbcs-httpd24-brotlito a version that resolves this vulnerability.Fixed in 0:1.0.6-40.jbcs.el7 - Upgrade
Upgrade
redhat/jbcs-httpd24-httpdto a version that resolves this vulnerability.Fixed in 0:2.4.37-66.jbcs.el7 - Upgrade
Upgrade
redhat/jbcs-httpd24-nghttp2to a version that resolves this vulnerability.Fixed in 0:1.39.2-35.jbcs.el7 - Upgrade
Upgrade
redhat/jbcs-httpd24-opensslto a version that resolves this vulnerability.Fixed in 1:1.1.1g-3.jbcs.el7 - Upgrade
Upgrade
redhat/jbcs-httpd24-openssl-chilto a version that resolves this vulnerability.Fixed in 0:1.0.0-3.jbcs.el7 - Upgrade
Upgrade
redhat/jbcs-httpd24-openssl-pkcs11to a version that resolves this vulnerability.Fixed in 0:0.4.10-18.jbcs.el7 - Upgrade
Upgrade
redhat/opensslto a version that resolves this vulnerability.Fixed in 0:1.0.1e-59.el6_10 - Upgrade
Upgrade
redhat/opensslto a version that resolves this vulnerability.Fixed in 1:1.0.2k-21.el7_9 - Upgrade
Upgrade
redhat/opensslto a version that resolves this vulnerability.Fixed in 1:1.0.1e-52.el7_2 - Upgrade
Upgrade
redhat/opensslto a version that resolves this vulnerability.Fixed in 1:1.0.1e-61.el7_3 - Upgrade
Upgrade
redhat/opensslto a version that resolves this vulnerability.Fixed in 1:1.0.2k-9.el7_4 - Upgrade
Upgrade
redhat/opensslto a version that resolves this vulnerability.Fixed in 1:1.0.2k-17.el7_6 - Upgrade
Upgrade
redhat/opensslto a version that resolves this vulnerability.Fixed in 1:1.0.2k-20.el7_7 - Upgrade
Upgrade
redhat/opensslto a version that resolves this vulnerability.Fixed in 1:1.1.1g-12.el8_3 - Upgrade
Upgrade
redhat/opensslto a version that resolves this vulnerability.Fixed in 1:1.1.1-9.el8_0 - Upgrade
Upgrade
redhat/opensslto a version that resolves this vulnerability.Fixed in 1:1.1.1c-3.el8_1 - Upgrade
Upgrade
redhat/opensslto a version that resolves this vulnerability.Fixed in 1:1.1.1c-16.el8_2 - Upgrade
Upgrade
redhat/tomcat-nativeto a version that resolves this vulnerability.Fixed in 0:1.2.23-23.redhat_23.ep7.el7 - Upgrade
Upgrade
redhat/jws5-tomcatto a version that resolves this vulnerability.Fixed in 0:9.0.36-9.redhat_8.1.el7 - Upgrade
Upgrade
redhat/jws5-tomcat-nativeto a version that resolves this vulnerability.Fixed in 0:1.2.25-3.redhat_3.el7 - Upgrade
Upgrade
redhat/jws5-tomcatto a version that resolves this vulnerability.Fixed in 0:9.0.36-9.redhat_8.1.el8 - Upgrade
Upgrade
redhat/jws5-tomcat-nativeto a version that resolves this vulnerability.Fixed in 0:1.2.25-3.redhat_3.el8 - Upgrade
Upgrade
debian/opensslto a version that resolves this vulnerability.Fixed in 1.1.1w-0+deb11u1Fixed in 1.1.1w-0+deb11u2Fixed in 3.0.15-1~deb12u1Fixed in 3.0.14-1~deb12u2Fixed in 3.5.0-1 - Upgrade
Upgrade
redhat/opensslto a version that resolves this vulnerability.Fixed in 1.1.1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.23.1Fixed in 12.20.1Fixed in 14.15.4Fixed in 15.5.0 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.23.1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 12.20.1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 14.15.4 - Upgrade
Upgrade
alpine/libresslto a version that resolves this vulnerability.Fixed in 3.1.5-r0 - Upgrade
Upgrade
alpine/opensslto a version that resolves this vulnerability.Fixed in 1.1.1i-r0 - Upgrade
Upgrade
alpine/openssl1.1-compatto a version that resolves this vulnerability.Fixed in 1.1.1i-r0 - Upgrade
Upgrade
alpine/openssl3to a version that resolves this vulnerability.Fixed in 1.1.1i-r0 - Upgrade
Upgrade
android/platform/external/boringsslto a version that resolves this vulnerability.Fixed in 11:2021-06-01 - Upgrade
Upgrade
OpenSSLto a version that resolves this vulnerability.Fixed in 1.0.2x - Upgrade
Upgrade
Node.jsto a version that resolves this vulnerability.Fixed in 15.5.0
Event History
Parent advisories
This vulnerability appears in the following advisories.
- RHSA-2021:0486
- RHSA-2021:0056
- RHSA-2020:5566
- RHSA-2020:5639
- RHSA-2020:5640
- RHSA-2020:5641
- RHSA-2020:5642
- RHSA-2020:5623
- RHSA-2020:5476
- RHSA-2020:5588
- RHSA-2020:5637
- RHSA-2020:5422
- RHSA-2021:0488
- RHSA-2021:0491
- RHSA-2021:0489
- RHSA-2021:0495
- RHSA-2021:0494
- IBM-6491653
- nodejs-january-2021-security-releases
- nodejs-release-v10.23.1
- nodejs-release-v12.20.1
- nodejs-release-v14.15.4
Frequently Asked Questions
What is the severity of CVE-2020-1971?
CVE-2020-1971 has been classified as a medium severity vulnerability, primarily impacting systems that utilize OpenSSL.
How do I fix CVE-2020-1971?
To fix CVE-2020-1971, update to the versions specified in the respective patches or releases provided by your software vendor.
Who is affected by CVE-2020-1971?
CVE-2020-1971 affects applications that use the OpenSSL library, particularly those built with specific versions noted in security advisories.
What type of vulnerability is CVE-2020-1971?
CVE-2020-1971 is a null pointer dereference vulnerability that can lead to a denial of service when exploited by an attacker.
What impact does CVE-2020-1971 have on systems?
The impact of CVE-2020-1971 is the potential for a remote attacker to cause a crash of the application, resulting in downtime.