CVE-2021-3712

HIGHNVD 7.48.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 8.0 because EPSS predicted 50% probability of exploitation within the next 30 days (98th percentile of EPSS-scored CVEs) when EchelonGraph scored this CVE. NVD baseline CVSS 7.4 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekElevated

Also known asEUVD-2022-4935 (ENISA EUVD) · GHSA-q9wj-f4qw-6vfj (GitHub Security Advisories)Source: ENISA EUVD

8.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 50%
CISA-KEV: Not listedEPSS PROB: 50%CVSS: 7.4Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a buffer holding the string data and a field holding the buffer length. This contrasts with normal C strings which are repesented as a buffer for the string data which is terminated with a NUL (0) byte. Although not a strict requirement, ASN.1 strings that are parsed using OpenSSL's own "d2i" functions (and other similar parsing functions) as well as any string whose value has been set with the ASN1_STRING_set() function will additionally NUL terminate the byte array in the ASN1_STRING structure. However, it is possible for applications to directly construct valid ASN1_STRING structures which do not NUL terminate the byte array by directly setting the "data" and "length" fields in the ASN1_STRING array. This can also happen by using the ASN1_STRING_set0() function. Numerous OpenSSL functions that print ASN.1 data have been found to assume that the ASN1_STRING byte array will be NUL terminated, even though this is not guaranteed for strings that have been directly constructed. Where an application requests an ASN.1 structure to be printed, and where that ASN.1 structure contains ASN1_STRINGs that have been directly constructed by the application without NUL terminating the "data" field, then a read buffer overrun can occur. The same thing can also occur during name constraints processing of certificates (for example if a certificate has been directly constructed by the application instead of loading it via the OpenSSL parsing functions, and the certificate contains non NUL terminated ASN1_STRING structures). It can also occur in the X509_get1_email(), X509_REQ_get1_email() and X509_get1_ocsp() functions. If a malicious actor can cause an application to directly construct an ASN1_STRING and then process it through one of the affected OpenSSL functions then this issue could be hit. This might result in a crash (causing a Denial of Service attack). It could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext). Fixed in OpenSSL 1.1.1l (Affected 1.1.1-1.1.1k). Fixed in OpenSSL 1.0.2za (Affected 1.0.2-1.0.2y).

CVSS v3
7.4
EG Score
8.0HIGHhigh confidence
EG Risk
53
EG Risk 53/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)
Severity74% × 45%
Impact severity (EG Severity): CVSS 7.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation50% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
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
50%
EPSS %ILE
98th
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 (8.0): severity, escalated by confirmed exploitation. This CVE's 8.0 is EPSS's lift toward 9.0 from its impact severity (EG Severity, CVSS 7.4 HIGH): a likelihood of exploitation, not impact.

EG Severity
7.4 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
50% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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

August 24, 2021

Last Modified

April 16, 2026

References (25)

15 of 25 shown · show the other 10

Patch Availability(12)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuqemu-efi-riscv64 (2024.02-2ubuntu0.6) @ noble2026-10-28ubuntu
ubuntuovmf (2020.11-4ubuntu0.1) @ hirsute2026-10-28ubuntu
ubuntulibssl-doc (1.1.1f-1ubuntu2.8) @ focal2026-10-28ubuntu
ubuntuopenssl (1.0.2g-1ubuntu4.20+esm1) @ xenial2026-10-28ubuntu
ubuntulibssl1.0-dev (1.0.2n-1ubuntu5.7) @ bionic2026-10-28ubuntu
redhatopenssl-1:1.0.2k-23.el7_92022-01-11redhat
redhatopenssl-1:1.1.1k-5.el8_52021-12-21redhat
redhatjws5-tomcat-vault-0:1.1.8-4.Final_redhat_00004.1.el8jws2021-11-30redhat
redhatpatch2021-11-30redhat
redhatopenssl2021-11-10redhat
redhatjbcs-httpd24-openssl-pkcs11-0:0.4.10-22.jbcs.el72021-11-10redhat
rustopenssl-src @ 111.16.0 (fixes < 111.16.0)—ghsa

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

(24 across 21 ecosystems)
Alpine:v3.15(2)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 1.1.1l-r0: fixed in 1.1.1l-r0
—
openssl3—
  • every version up to 1.1.1l-r0: fixed in 1.1.1l-r0
—
Alpine:v3.16(2)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 1.1.1l-r0: fixed in 1.1.1l-r0
—
openssl3—
  • every version up to 1.1.1l-r0: fixed in 1.1.1l-r0
—
Debian:9(2)
PackageVulnerable rangeFix by version rangeDependents
openssl1.1.0f-3 ... 1.1.0l-1~deb9u3 (17 versions)
  • every version up to 1.1.0l-1~deb9u4: fixed in 1.1.0l-1~deb9u4
—
openssl1.01.0.2l-2 ... 1.0.2u-1~deb9u5 (22 versions)
  • every version up to 1.0.2u-1~deb9u6: fixed in 1.0.2u-1~deb9u6
—
Alpine:v3.11(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 1.1.1l-r0: fixed in 1.1.1l-r0
—
Alpine:v3.12(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 1.1.1l-r0: fixed in 1.1.1l-r0
—
Alpine:v3.13(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 1.1.1l-r0: fixed in 1.1.1l-r0
—
Alpine:v3.14(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 1.1.1l-r0: fixed in 1.1.1l-r0
—
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 1.1.1l-r0: fixed in 1.1.1l-r0
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 1.1.1l-r0: fixed in 1.1.1l-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 1.1.1l-r0: fixed in 1.1.1l-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 1.1.1l-r0: fixed in 1.1.1l-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 1.1.1l-r0: fixed in 1.1.1l-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 1.1.1l-r0: fixed in 1.1.1l-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 1.1.1l-r0: fixed in 1.1.1l-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 1.1.1l-r0: fixed in 1.1.1l-r0
—
crates.io(1)
PackageVulnerable rangeFix by version rangeDependents
openssl-src—
  • every version up to 111.16.0: fixed in 111.16.0
  • 0.0.0-0 up to 111.16.0: fixed in 111.16.0
—
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
openssl1.1.1c-1 ... 1.1.1d-0+deb10u6 (7 versions)
  • every version up to 1.1.1d-0+deb10u7: fixed in 1.1.1d-0+deb10u7
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
openssl1.1.1k-1
  • every version up to 1.1.1k-1+deb11u1: fixed in 1.1.1k-1+deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 1.1.1l-1: fixed in 1.1.1l-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 1.1.1l-1: fixed in 1.1.1l-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 1.1.1l-1: fixed in 1.1.1l-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(6)

Data Freshness Timeline

(refreshed 9× in last 7d / 34× 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 95 of 209 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. 5 repeat rows among the latest 100 are merged into the row they repeat. The 114 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2021-3712?
CVE-2021-3712 is a high-severity vulnerability; its CVE record was published on August 24, 2021. ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a buffer holding the string data and a field holding the buffer length. This contrasts with normal C strings which are repesented as a buffer for the string data which is terminated with a NUL (0)…
When was CVE-2021-3712 made public?
CVE-2021-3712 was made public on August 24, 2021: 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 August 24, 2021. EchelonGraph's copy of the record carries a last-modified date of April 16, 2026; the record at its source may have been updated since.
Is CVE-2021-3712 actively exploited?
CVE-2021-3712 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 50% probability of exploitation in the next 30 days (98th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2021-3712?
CVE-2021-3712 has a CVSS v3 base score of 7.4 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 8.0 (HIGH).
How do I remediate CVE-2021-3712?
A fix for CVE-2021-3712 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2021-3712 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-2021-3712

Explore →

Is Your Infrastructure Affected by CVE-2021-3712?

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