CVE-2020-1971

MEDIUMNVD 5.95.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 5.9 from GitHub Security Advisory (severity: HIGH) published 2022-05-24. NVD baseline CVSS 5.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated

Also known asEUVD-2020-12761 (ENISA EUVD) · GHSA-whf2-mq76-2fhv (GitHub Security Advisories)Source: ENISA EUVD

5.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 7.0%CVSS: 5.9Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

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

CVSS v3
5.9
EG Score
5.9MEDIUMmedium confidence
EG Risk
43
EG Risk 43/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity59% × 45%
Impact severity (EG Severity): CVSS 5.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
7.0%
EPSS %ILE
94th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.9): severity, escalated by confirmed exploitation. This CVE's 5.9 is its impact severity (EG Severity), not escalated.

EG Severity
5.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
7.0% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

December 8, 2020

Last Modified

May 29, 2026

References (26)

15 of 26 shown · show the other 11

Patch Availability(18)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuopenssl (1.0.2g-1ubuntu4.18) @ xenial2026-10-25ubuntu
ubuntulibssl1.0.0-udeb (1.0.1-4ubuntu5.45) @ precise2026-10-25ubuntu
redhatopenshiftdo/odo-init-image-rhel7:1.1.3-22021-03-22redhat
redhatjbcs-httpd24-openssl-pkcs11-0:0.4.10-18.jbcs.el72021-02-11redhat
redhatopenssl2021-02-11redhat
redhatjws5-tomcat-native-0:1.2.25-3.redhat_3.el8jws2021-02-11redhat
redhattomcat-native-0:1.2.23-23.redhat_23.ep7.el72021-02-11redhat
redhatopenssl-0:1.0.1e-59.el6_102021-01-11redhat
redhatopenssl-1:1.0.2k-17.el7_62020-12-21redhat
redhatopenssl-1:1.0.1e-61.el7_32020-12-21redhat
redhatopenssl-1:1.1.1c-3.el8_12020-12-21redhat
redhatopenssl-1:1.0.2k-9.el7_42020-12-21redhat
redhatopenssl-1:1.0.1e-52.el7_22020-12-21redhat
redhatopenssl-1:1.0.2k-20.el7_72020-12-17redhat
redhatopenssl-1:1.0.2k-21.el7_92020-12-16redhat
redhatopenssl-1:1.1.1-9.el8_02020-12-16redhat
redhatopenssl-1:1.1.1g-12.el8_32020-12-15redhat
redhatopenssl-1:1.1.1c-16.el8_22020-12-15redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(26 across 22 ecosystems)
Alpine:v3.13(2)
PackageVulnerable rangeFix by version rangeDependents
libressl—
  • every version up to 3.1.5-r0: fixed in 3.1.5-r0
—
openssl—
  • 1.0.2 up to 1.1.1i-r0: fixed in 1.1.1i-r0
—
Alpine:v3.15(2)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 1.1.1i-r0: fixed in 1.1.1i-r0
—
openssl3—
  • every version up to 1.1.1i-r0: fixed in 1.1.1i-r0
—
Alpine:v3.16(2)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 1.1.1i-r0: fixed in 1.1.1i-r0
—
openssl3—
  • every version up to 1.1.1i-r0: fixed in 1.1.1i-r0
—
Debian:9(2)
PackageVulnerable rangeFix by version rangeDependents
openssl1.1.0f-3 ... 1.1.0l-1~deb9u1 (15 versions)
  • every version up to 1.1.0l-1~deb9u2: fixed in 1.1.0l-1~deb9u2
—
openssl1.01.0.2l-2 ... 1.0.2u-1~deb9u2 (19 versions)
  • every version up to 1.0.2u-1~deb9u3: fixed in 1.0.2u-1~deb9u3
—
Alpine:v3.10(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 1.1.1i-r0: fixed in 1.1.1i-r0
—
Alpine:v3.11(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 1.1.1i-r0: fixed in 1.1.1i-r0
—
Alpine:v3.12(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 1.1.1i-r0: fixed in 1.1.1i-r0
—
Alpine:v3.14(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 1.1.1i-r0: fixed in 1.1.1i-r0
—
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 1.1.1i-r0: fixed in 1.1.1i-r0
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 1.1.1i-r0: fixed in 1.1.1i-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 1.1.1i-r0: fixed in 1.1.1i-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 1.1.1i-r0: fixed in 1.1.1i-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 1.1.1i-r0: fixed in 1.1.1i-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 1.1.1i-r0: fixed in 1.1.1i-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 1.1.1i-r0: fixed in 1.1.1i-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 1.1.1i-r0: fixed in 1.1.1i-r0
—
Alpine:v3.9(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 1.1.1i-r0: fixed in 1.1.1i-r0
—
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
openssl1.1.1c-1, 1.1.1d-0+deb10u1, 1.1.1d-0+deb10u2, 1.1.1d-0+deb10u3
  • every version up to 1.1.1d-0+deb10u4: fixed in 1.1.1d-0+deb10u4
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 1.1.1i-1: fixed in 1.1.1i-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 1.1.1i-1: fixed in 1.1.1i-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 1.1.1i-1: fixed in 1.1.1i-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 1.1.1i-1: fixed in 1.1.1i-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(17)

Data Freshness Timeline

(refreshed 7× in last 7d / 38× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 97 of 197 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 3 repeat rows among the latest 100 are merged into the row they repeat. The 100 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:29 UTCEPSS rescoreEPSS 7.0% · 94th percentile
  2. 2026-10-31 16:28 UTCEPSS rescoreEPSS 7.0% · 94th percentile
  3. 2026-10-30 16:29 UTCEPSS rescoreEPSS 7.0% · 94th percentile
  4. 2026-10-29 16:28 UTCEPSS rescoreEPSS 7.0% · 94th percentile
  5. 2026-10-28 16:27 UTCEPSS rescoreEPSS 7.0% · 94th percentile
  6. 2026-10-27 16:27 UTCEPSS rescoreEPSS 7.0% · 94th percentile
  7. 2026-10-26 16:27 UTCEPSS rescoreEPSS 7.0% · 94th percentile
  8. 2026-10-25 18:48 UTCEG score recompute
  9. 2026-10-25 16:28 UTCEPSS rescoreEPSS 7.1% · 94th percentile
  10. 2026-10-25 02:17 UTCEG score recompute
  11. 2026-10-25 02:17 UTCVendor advisory
  12. 2026-10-25 02:17 UTCGHSA enrichmentGHSA-whf2-mq76-2fhv · GitHub severity HIGH · GitHub CVSS 5.9
  13. 2026-10-24 16:28 UTCEPSS rescoreEPSS 7.1% · 94th percentile
  14. 2026-10-23 16:27 UTCEPSS rescoreEPSS 7.1% · 94th percentile
  15. 2026-10-22 16:29 UTCEPSS rescoreEPSS 7.1% · 94th percentile
  16. 2026-10-21 16:28 UTCEPSS rescoreEPSS 7.1% · 94th percentile
  17. 2026-10-20 16:28 UTCEPSS rescoreEPSS 7.1% · 94th percentile
  18. 2026-10-19 16:27 UTCEPSS rescoreEPSS 7.1% · 94th percentile
  19. 2026-10-18 16:28 UTCEPSS rescoreEPSS 7.1% · 94th percentile
  20. 2026-10-18 09:30 UTCEG score recompute
  21. 2026-10-17 16:28 UTCEPSS rescoreEPSS 7.1% · 94th percentile
  22. 2026-10-16 16:33 UTCEPSS rescoreEPSS 7.1% · 94th percentile
  23. 2026-10-15 16:27 UTCEPSS rescoreEPSS 7.1% · 94th percentile
  24. 2026-10-14 16:28 UTCEPSS rescoreEPSS 7.1% · 94th percentile
  25. 2026-10-13 16:28 UTCEPSS rescoreEPSS 7.1% · 94th percentile
Show 72 more
  1. 2026-10-12 19:42 UTCEG score recompute
  2. 2026-10-12 16:29 UTCEPSS rescoreEPSS 7.1% · 94th percentile
  3. 2026-10-12 00:06 UTCEG score recompute
  4. 2026-10-11 13:43 UTCEPSS rescoreEPSS 7.1% · 94th percentile
  5. 2026-10-10 19:56 UTCEPSS rescoreEPSS 7.1% · 94th percentile
  6. 2026-10-09 20:04 UTCEPSS rescoreEPSS 7.1% · 94th percentile
  7. 2026-10-09 12:55 UTCOSV refresh
  8. 2026-10-08 16:38 UTCEPSS rescoreEPSS 7.1% · 94th percentile
  9. 2026-10-07 23:44 UTCEPSS rescoreEPSS 7.1% · 94th percentile
  10. 2026-10-06 15:13 UTCEPSS rescoreEPSS 7.1% · 94th percentile
  11. 2026-10-05 17:39 UTCEPSS rescoreEPSS 7.1% · 94th percentile
  12. 2026-10-04 23:18 UTCEPSS rescoreEPSS 7.1% · 94th percentile
  13. 2026-10-03 14:22 UTCEPSS rescoreEPSS 7.1% · 94th percentile
  14. 2026-10-02 16:22 UTCEPSS rescoreEPSS 7.1% · 94th percentile
  15. 2026-09-30 15:14 UTCEG score recompute
  16. 2026-09-30 14:59 UTCEPSS rescoreEPSS 7.1% · 93rd percentile
  17. 2026-09-27 13:40 UTCEPSS rescoreEPSS 7.1% · 93rd percentile
  18. 2026-09-26 15:54 UTCEPSS rescoreEPSS 7.1% · 93rd percentile
  19. 2026-09-26 00:20 UTCEPSS rescoreEPSS 7.1% · 93rd percentile
  20. 2026-09-24 14:00 UTCEPSS rescoreEPSS 7.1% · 93rd percentile
  21. 2026-09-22 14:43 UTCEPSS rescoreEPSS 7.1% · 93rd percentile
  22. 2026-09-21 20:28 UTCEPSS rescoreEPSS 7.1% · 93rd percentile
  23. 2026-09-19 20:03 UTCOSV refresh
  24. 2026-09-18 19:23 UTCEPSS rescoreEPSS 7.1% · 93rd percentile
  25. 2026-09-17 19:22 UTCEPSS rescoreEPSS 7.1% · 93rd percentile
  26. 2026-09-16 14:04 UTCEPSS rescoreEPSS 7.1% · 93rd percentile
  27. 2026-09-15 03:06 UTCEPSS rescoreEPSS 7.1% · 93rd percentile
  28. 2026-09-13 16:42 UTCEPSS rescoreEPSS 7.1% · 93rd percentile
  29. 2026-09-12 14:56 UTCEPSS rescoreEPSS 7.1% · 93rd percentile
  30. 2026-09-11 14:48 UTCEPSS rescoreEPSS 7.1% · 93rd percentile
  31. 2026-09-11 09:32 UTCEPSS rescoreEPSS 7.1% · 93rd percentile
  32. 2026-09-10 09:29 UTCEPSS rescoreEPSS 7.1% · 93rd percentile
  33. 2026-09-08 21:56 UTCEPSS rescoreEPSS 7.1% · 93rd percentile
  34. 2026-09-07 15:57 UTCEPSS rescoreEPSS 7.1% · 93rd percentile
  35. 2026-09-06 13:44 UTCEPSS rescoreEPSS 7.1% · 93rd percentile
  36. 2026-09-05 15:24 UTCEPSS rescoreEPSS 7.1% · 93rd percentile
  37. 2026-09-04 13:57 UTCEPSS rescoreEPSS 7.1% · 93rd percentile
  38. 2026-09-04 05:03 UTCEPSS rescoreEPSS 7.1% · 93rd percentile
  39. 2026-09-02 14:08 UTCEPSS rescoreEPSS 7.1% · 93rd percentile
  40. 2026-09-01 03:32 UTCEPSS rescoreEPSS 7.0% · 93rd percentile
  41. 2026-08-31 23:34 UTCOSV refresh
  42. 2026-08-30 19:14 UTCEPSS rescoreEPSS 7.0% · 93rd percentile
  43. 2026-08-30 01:18 UTCEPSS rescoreEPSS 7.0% · 93rd percentile
  44. 2026-08-27 14:21 UTCEPSS rescoreEPSS 7.0% · 93rd percentile
  45. 2026-08-26 14:42 UTCEPSS rescoreEPSS 7.0% · 93rd percentile
  46. 2026-08-25 13:45 UTCEPSS rescoreEPSS 7.0% · 93rd percentile
  47. 2026-08-21 23:45 UTCEPSS rescoreEPSS 7.0% · 93rd percentile
  48. 2026-08-20 22:52 UTCEPSS rescoreEPSS 7.0% · 93rd percentile
  49. 2026-08-19 17:00 UTCEPSS rescoreEPSS 7.0% · 93rd percentile
  50. 2026-08-18 13:44 UTCEPSS rescoreEPSS 7.0% · 93rd percentile
  51. 2026-08-17 13:43 UTCEPSS rescoreEPSS 7.0% · 93rd percentile
  52. 2026-08-16 14:52 UTCEPSS rescoreEPSS 7.0% · 93rd percentile
  53. 2026-08-16 02:11 UTCEPSS rescoreEPSS 7.0% · 93rd percentile
  54. 2026-08-15 01:26 UTCEPSS rescoreEPSS 7.0% · 93rd percentile
  55. 2026-08-15 00:24 UTCOSV refresh
  56. 2026-08-13 21:57 UTCEPSS rescoreEPSS 7.0% · 93rd percentile
  57. 2026-08-12 13:47 UTCEPSS rescoreEPSS 7.0% · 93rd percentile
  58. 2026-08-09 13:43 UTCEPSS rescoreEPSS 7.0% · 93rd percentile
  59. 2026-08-08 16:33 UTCEPSS rescoreEPSS 7.0% · 93rd percentile
  60. 2026-08-07 16:23 UTCEPSS rescoreEPSS 7.0% · 93rd percentile
  61. 2026-08-06 13:43 UTCEPSS rescoreEPSS 7.0% · 93rd percentile
  62. 2026-08-05 19:14 UTCEPSS rescoreEPSS 7.0% · 93rd percentile
  63. 2026-08-04 15:06 UTCEPSS rescoreEPSS 7.0% · 93rd percentile
  64. 2026-08-04 10:34 UTCEPSS rescoreEPSS 7.0% · 93rd percentile
  65. 2026-08-03 10:32 UTCEPSS rescoreEPSS 7.0% · 93rd percentile
  66. 2026-08-02 02:23 UTCEPSS rescoreEPSS 7.0% · 93rd percentile
  67. 2026-08-01 04:12 UTCEPSS rescoreEPSS 7.0% · 93rd percentile
  68. 2026-07-30 16:25 UTCEPSS rescoreEPSS 7.0% · 93rd percentile
  69. 2026-07-30 13:14 UTCOSV refresh
  70. 2026-07-30 01:27 UTCEPSS rescoreEPSS 7.0% · 93rd percentile
  71. 2026-07-28 15:32 UTCEPSS rescoreEPSS 7.0% · 93rd percentile
  72. 2026-07-27 14:06 UTCEPSS rescoreEPSS 7.0% · 93rd percentile

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 GitHub PoC). Defenders should treat patch urgency accordingly.

  • GitHub PoCMBHudson/CVE-2020-1971
    Published Dec 9, 2020

    CVE-2020-1971 Auto Scan & Remote Exploit Script. Auto Local Scan & Patch Script.

    Open source ↗

Frequently asked(5)

What is CVE-2020-1971?
CVE-2020-1971 is a medium-severity vulnerability; its CVE record was published on December 8, 2020. 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…
When was CVE-2020-1971 made public?
CVE-2020-1971 was made public on December 8, 2020: that is the date its CVE record's CNA, OpenSSL Software Foundation, gives for when the vulnerability was made public. The CVE record itself was published on December 8, 2020. EchelonGraph's copy of the record carries a last-modified date of May 29, 2026; the record at its source may have been updated since.
Is CVE-2020-1971 actively exploited?
CVE-2020-1971 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 7.0% probability of exploitation in the next 30 days (94th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2020-1971?
CVE-2020-1971 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2020-1971?
A fix for CVE-2020-1971 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2020-1971 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-1971

Explore →

Is Your Infrastructure Affected by CVE-2020-1971?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.