Skip to content
Noroxi
CVE-2020-1971· NVD / CVE Program· CNA openssl

EDIPARTYNAME NULL pointer dereference

Noroxi assessment

Priority: Monitor (action score 25/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 7% (FIRST EPSS); higher than 94.1% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: openssl (Alpine:v3.10) 1.1.1i-r0; libressl (Alpine:v3.13) 3.1.5-r0; openssl3 (Alpine:v3.15) 1.1.1i-r0.
  • Mentioned 6 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to openssl (Alpine:v3.10) 1.1.1i-r0; libressl (Alpine:v3.13) 3.1.5-r0; openssl3 (Alpine:v3.15) 1.1.1i-r0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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).

MediumCVSS 5.9 · v3.1—Proof of concept Fix available
Published
Dec 8, 2020
Updated
Jun 16, 2026
EPSS
7.0% · 94th percentile

Report tools

JSON

Action score

25

Monitor

Low priority for now.

CVSS
23 / 40 · 5.9 / 10
CISA KEV
0 / 30 · Not listed
EPSS
2 / 30 · 7.0%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2020-1971

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
opensslopenssl
debiandebian linux
fedoraprojectfedora
oracleapi gateway
oraclebusiness intelligence
oraclecommunications cloud native core network function cloud native environment
oraclecommunications diameter intelligence hub
oraclecommunications session border controller
oraclecommunications session router
oraclecommunications subscriber-aware load balancer
oraclecommunications unified session manager
oracleenterprise communications broker

and 34 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • nodejs node.js15.0.0 and later · before 15.5.0
  • nodejs node.js12.13.0 and later · before 12.20.1
  • nodejs node.js14.0.0 and later · up to 14.14.0 inclusive
  • nodejs node.js14.15.0 and later · before 14.15.4
  • nodejs node.js10.0.0 and later · up to 10.12.0 inclusive
  • nodejs node.js10.13.0 and later · before 10.23.1
  • nodejs node.js12.0.0 and later · up to 12.12.0 inclusive
  • oracle mysqlup to 8.0.22 inclusive
  • oracle mysql serverup to 5.7.32 inclusive
  • oracle mysql server8.0.15 and later · up to 8.0.22 inclusive

Versions reported by the vendor

Affected version ranges reported by the assigning authority (openssl). Independent of NVD's CPE analysis and usually ahead of it.

  • OpenSSL OpenSSL

    • 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

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.10opensslfrom 1.0.2 · before 1.1.1i-r01.1.1i-r0
Alpine:v3.13libresslbefore 3.1.5-r03.1.5-r0
Alpine:v3.15openssl3before 1.1.1i-r01.1.1i-r0
Debian:10opensslbefore 1.1.1d-0+deb10u41.1.1d-0+deb10u4
Debian:12opensslbefore 1.1.1i-11.1.1i-1
Debian:9opensslbefore 1.1.0l-1~deb9u21.1.0l-1~deb9u2
Debian:9openssl1.0before 1.0.2u-1~deb9u31.0.2u-1~deb9u3
openSUSE:Leap 15.1nodejs10before 10.23.1-lp151.2.15.110.23.1-lp151.2.15.1
openSUSE:Leap 15.1openssl-1_0_0before 1.0.2p-lp151.5.20.11.0.2p-lp151.5.20.1
openSUSE:Leap 15.1openssl-1_1before 1.1.0i-lp151.8.12.21.1.0i-lp151.8.12.2
openSUSE:Leap 15.2nodejs10before 10.23.1-lp152.2.9.110.23.1-lp152.2.9.1
openSUSE:Leap 15.2nodejs12before 12.20.1-lp152.3.9.112.20.1-lp152.3.9.1
openSUSE:Leap 15.2openssl-1_0_0before 1.0.2p-lp152.8.9.11.0.2p-lp152.8.9.1
openSUSE:Leap 15.2openssl-1_1before 1.1.1d-lp152.7.9.11.1.1d-lp152.7.9.1
openSUSE:Tumbleweedmatrix-synapsebefore 1.43.0-1.11.43.0-1.1
openSUSE:Tumbleweedopenssl-1_0_0before 1.0.2u-12.11.0.2u-12.1
openSUSE:Tumbleweedopenssl-3before 3.0.1-1.13.0.1-1.1
Red Hat:enterprise_linux:7::clientopensslbefore 1:1.0.2k-21.el7_91:1.0.2k-21.el7_9
Red Hat:enterprise_linux:7::clientopenssl-debuginfobefore 1:1.0.2k-21.el7_91:1.0.2k-21.el7_9
Red Hat:enterprise_linux:7::clientopenssl-develbefore 1:1.0.2k-21.el7_91:1.0.2k-21.el7_9
Red Hat:enterprise_linux:7::clientopenssl-libsbefore 1:1.0.2k-21.el7_91:1.0.2k-21.el7_9
Red Hat:enterprise_linux:7::clientopenssl-perlbefore 1:1.0.2k-21.el7_91:1.0.2k-21.el7_9
Red Hat:enterprise_linux:7::clientopenssl-staticbefore 1:1.0.2k-21.el7_91:1.0.2k-21.el7_9
Red Hat:enterprise_linux:8::baseosopensslbefore 1:1.1.1g-12.el8_31:1.1.1g-12.el8_3

+96

Other highest-scoring records for the same primary product.

  • CVE-2014-0160The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packets, which allows remKEV
    90Now
  • CVE-2021-3711SM2 Decryption Buffer Overflow
    65This week
  • CVE-2003-0545Double free vulnerability in OpenSSL 0.9.7 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code
    65This week
  • CVE-2016-2108The ASN.1 implementation in OpenSSL before 1.0.1o and 1.0.2 before 1.0.2c allows remote attackers to execute arbitrary code or cause a denia
    62This week
  • CVE-2016-6309statem/statem.c in OpenSSL 1.1.0a does not consider memory-block movement after a realloc call, which allows remote attackers to cause a den
    60This week
  • CVE-2022-3786X.509 Email Address Variable Length Buffer Overflow
    58Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
alpine:libressl3.1.5-r0 · Alpine:v3.13Package registry (OSV)
alpine:openssl1.1.1i-r0 · Alpine:v3.10Package registry (OSV)
alpine:openssl31.1.1i-r0 · Alpine:v3.15Package registry (OSV)
debian:openssl1.1.1i-1 · Debian:12Package registry (OSV)
debian:openssl1.01.0.2u-1~deb9u3 · Debian:9Package registry (OSV)
opensuse:matrix-synapse1.43.0-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:nodejs1010.23.1-lp152.2.9.1 · openSUSE:Leap 15.2Package registry (OSV)
opensuse:nodejs1212.20.1-lp152.3.9.1 · openSUSE:Leap 15.2Package registry (OSV)
opensuse:openssl-1_0_01.0.2p-lp152.8.9.1 · openSUSE:Leap 15.2Package registry (OSV)
opensuse:openssl-1_11.1.1d-lp152.7.9.1 · openSUSE:Leap 15.2Package registry (OSV)
opensuse:openssl-33.0.1-1.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:jbcs-httpd24-brotli0:1.0.6-40.jbcs.el7 · Red Hat:jboss_core_services:1::el7Package registry (OSV)
red hat:jbcs-httpd24-brotli-debuginfo0:1.0.6-40.jbcs.el7 · Red Hat:jboss_core_services:1::el7Package registry (OSV)
red hat:jbcs-httpd24-brotli-devel0:1.0.6-40.jbcs.el7 · Red Hat:jboss_core_services:1::el7Package registry (OSV)
red hat:jbcs-httpd24-httpd0:2.4.37-66.jbcs.el7 · Red Hat:jboss_core_services:1::el7Package registry (OSV)
red hat:openssl1:1.1.1c-16.el8_2 · Red Hat:rhel_eus:8.2::baseosPackage registry (OSV)
red hat:openssl-debuginfo1:1.1.1c-16.el8_2 · Red Hat:rhel_eus:8.2::baseosPackage registry (OSV)
red hat:openssl-debugsource1:1.1.1c-16.el8_2 · Red Hat:rhel_eus:8.2::baseosPackage registry (OSV)
red hat:openssl-devel1:1.1.1c-16.el8_2 · Red Hat:rhel_eus:8.2::baseosPackage registry (OSV)
red hat:openssl-libs1:1.1.1c-16.el8_2 · Red Hat:rhel_eus:8.2::baseosPackage registry (OSV)
red hat:openssl-libs-debuginfo1:1.1.1c-16.el8_2 · Red Hat:rhel_eus:8.2::baseosPackage registry (OSV)
red hat:openssl-perl1:1.1.1c-16.el8_2 · Red Hat:rhel_eus:8.2::baseosPackage registry (OSV)
red hat:openssl-static1:1.0.2k-21.el7_9 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
suse:nodejs1010.23.1-1.30.1 · SUSE:Linux Enterprise Module for Web and Scripting 15 SP1Package registry (OSV)
suse:nodejs1212.20.1-4.10.1 · SUSE:Linux Enterprise Module for Web and Scripting 15 SP2Package registry (OSV)
suse:openssl1.0.2j-60.63.1 · SUSE:HPE Helion OpenStack 8Package registry (OSV)
suse:openssl-1_0_01.0.2p-3.30.1 · SUSE:OpenStack Cloud 9Package registry (OSV)
suse:openssl-1_11.1.0i-14.12.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP1Package registry (OSV)
suse:openssl11.0.1g-0.58.30.1 · SUSE:Linux Enterprise Server 11-SECURITYPackage registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:72020-12-09

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoCsame day
  3. TodayOct 16, 2026+2138 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records