CVE-2020-1971: EDIPARTYNAME NULL pointer dereference

Published Dec 2, 2020
·
Updated

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

141 affected componentsFixes available
redhat/jbcs-httpd24-brotli<0:1.0.6-40.jbcs.el7
0:1.0.6-40.jbcs.el7
redhat/jbcs-httpd24-httpd<0:2.4.37-66.jbcs.el7
0:2.4.37-66.jbcs.el7
redhat/jbcs-httpd24-nghttp2<0:1.39.2-35.jbcs.el7
0:1.39.2-35.jbcs.el7
redhat/jbcs-httpd24-openssl<1:1.1.1g-3.jbcs.el7
1:1.1.1g-3.jbcs.el7
redhat/jbcs-httpd24-openssl-chil<0:1.0.0-3.jbcs.el7
0:1.0.0-3.jbcs.el7
redhat/jbcs-httpd24-openssl-pkcs11<0:0.4.10-18.jbcs.el7
0:0.4.10-18.jbcs.el7
redhat/openssl<0:1.0.1e-59.el6_10
0:1.0.1e-59.el6_10
redhat/openssl<1:1.0.2k-21.el7_9
1:1.0.2k-21.el7_9
redhat/openssl<1:1.0.1e-52.el7_2
1:1.0.1e-52.el7_2
redhat/openssl<1:1.0.1e-61.el7_3
1:1.0.1e-61.el7_3
redhat/openssl<1:1.0.2k-9.el7_4
1:1.0.2k-9.el7_4
redhat/openssl<1:1.0.2k-17.el7_6
1:1.0.2k-17.el7_6
redhat/openssl<1:1.0.2k-20.el7_7
1:1.0.2k-20.el7_7
redhat/openssl<1:1.1.1g-12.el8_3
1:1.1.1g-12.el8_3
redhat/openssl<1:1.1.1-9.el8_0
1:1.1.1-9.el8_0
redhat/openssl<1:1.1.1c-3.el8_1
1:1.1.1c-3.el8_1
redhat/openssl<1:1.1.1c-16.el8_2
1:1.1.1c-16.el8_2
redhat/tomcat-native<0:1.2.23-23.redhat_23.ep7.el7
0:1.2.23-23.redhat_23.ep7.el7
redhat/jws5-tomcat<0:9.0.36-9.redhat_8.1.el7
0:9.0.36-9.redhat_8.1.el7
redhat/jws5-tomcat-native<0:1.2.25-3.redhat_3.el7
0:1.2.25-3.redhat_3.el7
redhat/jws5-tomcat<0:9.0.36-9.redhat_8.1.el8
0:9.0.36-9.redhat_8.1.el8
redhat/jws5-tomcat-native<0:1.2.25-3.redhat_3.el8
0:1.2.25-3.redhat_3.el8
IBM Security Verify Bridge<=All
debian/openssl
1.1.1w-0+deb11u11.1.1w-0+deb11u23.0.15-1~deb12u13.0.14-1~deb12u23.5.0-1
OpenSSL OpenSSL>=1.0.2<1.0.2x
OpenSSL OpenSSL>=1.1.1<1.1.1i
Debian Debian Linux=9.0
Debian Debian Linux=10.0
Fedoraproject Fedora=32
Fedoraproject Fedora=33
Oracle API Gateway=11.1.2.4.0
Oracle Business Intelligence=5.5.0.0.0
Oracle Business Intelligence=5.9.0.0.0
Oracle Business Intelligence=12.2.1.3.0
Oracle Business Intelligence=12.2.1.4.0
Oracle Communications Cloud Native Core Network Function Cloud Native Environment=1.10.0
Oracle Communications Diameter Intelligence Hub>=8.0.0<=8.1.0
Oracle Communications Diameter Intelligence Hub>=8.2.0<=8.2.3
Oracle Communications Session Border Controller=cz8.2
Oracle Communications Session Border Controller=cz8.3
Oracle Communications Session Border Controller=cz8.4
Oracle Communications Session Router=cz8.2
Oracle Communications Session Router=cz8.3
Oracle Communications Session Router=cz8.4
Oracle Communications Subscriber-aware Load Balancer=cz8.2
Oracle Communications Subscriber-aware Load Balancer=cz8.3
Oracle Communications Subscriber-aware Load Balancer=cz8.4
Oracle Communications Unified Session Manager=scz8.2.5
Oracle Enterprise Communications Broker=pcz3.1
Oracle Enterprise Communications Broker=pcz3.2
Oracle Enterprise Communications Broker=pcz3.3
Oracle Enterprise Manager Base Platform=13.3.0.0
Oracle Enterprise Manager Base Platform=13.4.0.0
Oracle Enterprise Manager For Storage Management=13.4.0.0
Oracle Enterprise Manager Ops Center=12.4.0.0
Oracle Enterprise Session Border Controller=cz8.2
Oracle Enterprise Session Border Controller=cz8.3
Oracle Enterprise Session Border Controller=cz8.4
Oracle Essbase=21.2
Oracle GraalVM=19.3.4
Oracle GraalVM=20.3.0
Oracle HTTP Server=12.2.1.4.0
Oracle JD Edwards EnterpriseOne Tools<9.2.5.3
Oracle Jd Edwards World Security=a9.4
Oracle MySQL<=8.0.22
Oracle MySQL Server<=5.7.32
Oracle MySQL Server>=8.0.15<=8.0.22
Oracle PeopleSoft Enterprise PeopleTools=8.56
Oracle PeopleSoft Enterprise PeopleTools=8.57
Oracle PeopleSoft Enterprise PeopleTools=8.58
NetApp Active Iq Unified Manager Vmware Vsphere
NetApp Active Iq Unified Manager Windows
NetApp Clustered Data Ontap Antivirus Connector
NetApp Data Ontap 7-mode
NetApp E-Series SANtricity OS Controller>=11.0.0<=11.60.3
NetApp Hci Management Node
NetApp Manageability Software Development Kit
NetApp OnCommand Insight
NetApp OnCommand Workflow Automation
NetApp Plug-in For Symantec Netbackup
NetApp Santricity Smi-s Provider
NetApp Snapcenter
NetApp Solidfire
NetApp Hci Compute Node
NetApp Hci Storage Node
NetApp Ef600a Firmware
NetApp Ef600a
NetApp Aff A250 Firmware
NetApp Aff A250
Tenable Log Correlation Engine<6.0.9
Tenable Nessus Network Monitor<5.13.1
Siemens Sinec Infrastructure Network Services<1.0.1.1
Nodejs Node.js>=10.0.0<=10.12.0
Nodejs Node.js>=10.13.0<10.23.1
Nodejs Node.js>=12.0.0<=12.12.0
Nodejs Node.js>=12.13.0<12.20.1
Nodejs Node.js>=14.0.0<=14.14.0
Nodejs Node.js>=14.15.0<14.15.4
Nodejs Node.js>=15.0.0<15.5.0
redhat/openssl<1.1.1
1.1.1
All of the following
NetApp Ef600a Firmware
NetApp Ef600a
All of the following
NetApp Aff A250 Firmware
NetApp Aff A250
Node.js Node.js>=10.0.0<10.23.1, >=12.0.0<12.20.1, >=14.0.0<14.15.4, >=15.0.0<15.5.0
10.23.112.20.114.15.415.5.0
Node.js Node.js>=10.0.0<10.23.1
10.23.1
Node.js Node.js>=12.0.0<12.20.1
12.20.1
Node.js Node.js>=14.0.0<14.15.4
14.15.4
android/platform/external/boringssl>=11:0<11:2021-06-01
11:2021-06-01
alpine/libressl<3.1.5-r0
3.1.5-r0
alpine/libressl<3.1.5-r0
3.1.5-r0
alpine/libressl<3.1.5-r0
3.1.5-r0
alpine/libressl<3.1.5-r0
3.1.5-r0
alpine/libressl<3.1.5-r0
3.1.5-r0
alpine/libressl<3.1.5-r0
3.1.5-r0
alpine/libressl<3.1.5-r0
3.1.5-r0
alpine/libressl<3.1.5-r0
3.1.5-r0
alpine/libressl<3.1.5-r0
3.1.5-r0
alpine/libressl<3.1.5-r0
3.1.5-r0
alpine/libressl<3.1.5-r0
3.1.5-r0
alpine/libressl<3.1.5-r0
3.1.5-r0
alpine/openssl>=1.0.2<1.1.1i-r0
1.1.1i-r0
alpine/openssl>=1.0.2<1.1.1i-r0
1.1.1i-r0
alpine/openssl>=1.0.2<1.1.1i-r0
1.1.1i-r0
alpine/openssl>=1.0.2<1.1.1i-r0
1.1.1i-r0
alpine/openssl>=1.0.2<1.1.1i-r0
1.1.1i-r0
alpine/openssl>=1.0.2<1.1.1i-r0
1.1.1i-r0
alpine/openssl>=1.0.2<1.1.1i-r0
1.1.1i-r0
alpine/openssl>=1.0.2<1.1.1i-r0
1.1.1i-r0
alpine/openssl>=1.0.2<1.1.1i-r0
1.1.1i-r0
alpine/openssl>=1.0.2<1.1.1i-r0
1.1.1i-r0
alpine/openssl>=1.0.2<1.1.1i-r0
1.1.1i-r0
alpine/openssl>=1.0.2<1.1.1i-r0
1.1.1i-r0
alpine/openssl>=1.0.2<1.1.1i-r0
1.1.1i-r0
alpine/openssl>=1.0.2<1.1.1i-r0
1.1.1i-r0
alpine/openssl>=1.0.2<1.1.1i-r0
1.1.1i-r0
alpine/openssl>=1.0.2<1.1.1i-r0
1.1.1i-r0
alpine/openssl1.1-compat<1.1.1i-r0
1.1.1i-r0
alpine/openssl1.1-compat<1.1.1i-r0
1.1.1i-r0
alpine/openssl3<1.1.1i-r0
1.1.1i-r0
alpine/openssl3<1.1.1i-r0
1.1.1i-r0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/jbcs-httpd24-brotli to a version that resolves this vulnerability.

    Fixed in 0:1.0.6-40.jbcs.el7
  2. Upgrade

    Upgrade redhat/jbcs-httpd24-httpd to a version that resolves this vulnerability.

    Fixed in 0:2.4.37-66.jbcs.el7
  3. Upgrade

    Upgrade redhat/jbcs-httpd24-nghttp2 to a version that resolves this vulnerability.

    Fixed in 0:1.39.2-35.jbcs.el7
  4. Upgrade

    Upgrade redhat/jbcs-httpd24-openssl to a version that resolves this vulnerability.

    Fixed in 1:1.1.1g-3.jbcs.el7
  5. Upgrade

    Upgrade redhat/jbcs-httpd24-openssl-chil to a version that resolves this vulnerability.

    Fixed in 0:1.0.0-3.jbcs.el7
  6. Upgrade

    Upgrade redhat/jbcs-httpd24-openssl-pkcs11 to a version that resolves this vulnerability.

    Fixed in 0:0.4.10-18.jbcs.el7
  7. Upgrade

    Upgrade redhat/openssl to a version that resolves this vulnerability.

    Fixed in 0:1.0.1e-59.el6_10
  8. Upgrade

    Upgrade redhat/openssl to a version that resolves this vulnerability.

    Fixed in 1:1.0.2k-21.el7_9
  9. Upgrade

    Upgrade redhat/openssl to a version that resolves this vulnerability.

    Fixed in 1:1.0.1e-52.el7_2
  10. Upgrade

    Upgrade redhat/openssl to a version that resolves this vulnerability.

    Fixed in 1:1.0.1e-61.el7_3
  11. Upgrade

    Upgrade redhat/openssl to a version that resolves this vulnerability.

    Fixed in 1:1.0.2k-9.el7_4
  12. Upgrade

    Upgrade redhat/openssl to a version that resolves this vulnerability.

    Fixed in 1:1.0.2k-17.el7_6
  13. Upgrade

    Upgrade redhat/openssl to a version that resolves this vulnerability.

    Fixed in 1:1.0.2k-20.el7_7
  14. Upgrade

    Upgrade redhat/openssl to a version that resolves this vulnerability.

    Fixed in 1:1.1.1g-12.el8_3
  15. Upgrade

    Upgrade redhat/openssl to a version that resolves this vulnerability.

    Fixed in 1:1.1.1-9.el8_0
  16. Upgrade

    Upgrade redhat/openssl to a version that resolves this vulnerability.

    Fixed in 1:1.1.1c-3.el8_1
  17. Upgrade

    Upgrade redhat/openssl to a version that resolves this vulnerability.

    Fixed in 1:1.1.1c-16.el8_2
  18. Upgrade

    Upgrade redhat/tomcat-native to a version that resolves this vulnerability.

    Fixed in 0:1.2.23-23.redhat_23.ep7.el7
  19. Upgrade

    Upgrade redhat/jws5-tomcat to a version that resolves this vulnerability.

    Fixed in 0:9.0.36-9.redhat_8.1.el7
  20. Upgrade

    Upgrade redhat/jws5-tomcat-native to a version that resolves this vulnerability.

    Fixed in 0:1.2.25-3.redhat_3.el7
  21. Upgrade

    Upgrade redhat/jws5-tomcat to a version that resolves this vulnerability.

    Fixed in 0:9.0.36-9.redhat_8.1.el8
  22. Upgrade

    Upgrade redhat/jws5-tomcat-native to a version that resolves this vulnerability.

    Fixed in 0:1.2.25-3.redhat_3.el8
  23. Upgrade

    Upgrade debian/openssl to 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
  24. Upgrade

    Upgrade redhat/openssl to a version that resolves this vulnerability.

    Fixed in 1.1.1
  25. 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
  26. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.23.1
  27. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 12.20.1
  28. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 14.15.4
  29. Upgrade

    Upgrade alpine/libressl to a version that resolves this vulnerability.

    Fixed in 3.1.5-r0
  30. Upgrade

    Upgrade alpine/openssl to a version that resolves this vulnerability.

    Fixed in 1.1.1i-r0
  31. Upgrade

    Upgrade alpine/openssl1.1-compat to a version that resolves this vulnerability.

    Fixed in 1.1.1i-r0
  32. Upgrade

    Upgrade alpine/openssl3 to a version that resolves this vulnerability.

    Fixed in 1.1.1i-r0
  33. Upgrade

    Upgrade android/platform/external/boringssl to a version that resolves this vulnerability.

    Fixed in 11:2021-06-01
  34. Upgrade

    Upgrade OpenSSL to a version that resolves this vulnerability.

    Fixed in 1.0.2x
  35. Upgrade

    Upgrade Node.js to a version that resolves this vulnerability.

    Fixed in 15.5.0

Event History

Dec 2, 2020
Data Sourced
via Red Hat·02:46 AM
DescriptionSeverityAffected Software
Dec 8, 2020
CVE Published
12:00 AM
CVE Published
via MITRE·03:30 PM
Data Sourced
via MITRE·03:30 PM
DescriptionWeakness
Data Sourced
via NVD·04:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·04:15 PM
DescriptionSeverityAffected Software
Dec 9, 2020
Exploit Published
via GitHub·09:32 PM
Jan 4, 2021
Data Sourced
via Node.js·06:17 PM
SeverityAffected Software
Data Sourced
via Node.js·07:30 PM
Description
Jun 1, 2021
Advisory Published
via OSV·12:00 AM

Frequently Asked Questions

1

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.

2

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.

3

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.

4

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.

5

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203