CVE-2022-3602

CRITICALNVD 7.59.0
EchelonGraph scoreHIGH confidence

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

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

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this weekElevated
9.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 91%
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 91%CVSS: 7.5Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed the malicious certificate or for the application to continue certificate verification despite failure to construct a path to a trusted issuer. An attacker can craft a malicious email address to overflow four attacker-controlled bytes on the stack. This buffer overflow could result in a crash (causing a denial of service) or potentially remote code execution. Many platforms implement stack overflow protections which would mitigate against the risk of remote code execution. The risk may be further mitigated based on stack layout for any given platform/compiler. Pre-announcements of CVE-2022-3602 described this issue as CRITICAL. Further analysis based on some of the mitigating factors described above have led this to be downgraded to HIGH. Users are still encouraged to upgrade to a new version as soon as possible. In a TLS client, this can be triggered by connecting to a malicious server. In a TLS server, this can be triggered if the server requests client authentication and a malicious client connects. Fixed in OpenSSL 3.0.7 (Affected 3.0.0,3.0.1,3.0.2,3.0.3,3.0.4,3.0.5,3.0.6).

CVSS v3
7.5
EG Score
9.0CRITICALhigh confidence
EG Risk
85
EG Risk 85/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation91% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
91%
EPSS %ILE
99th
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 (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is EPSS's lift toward 9.0 from its impact severity (EG Severity, CVSS 7.5 HIGH): a likelihood of exploitation, not impact.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
91% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-22). 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 low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

November 1, 2022

Last Modified

April 14, 2026

Advisory Details (10)

Auto-updated Oct 15, 2026
Patch available.
Web page

oss-security - Re: OpenSSL X.509 Email Address 4-byte Buffer Overflow (CVE-2022-3602), X.509 Email Address Variable Length Buffer Overflow (CVE-2022-3786)

http://www.openwall.com/lists/oss-security/2022/11/02/1
Web page

oss-security - Re: OpenSSL X.509 Email Address 4-byte Buffer Overflow (CVE-2022-3602), X.509 Email Address Variable Length Buffer Overflow (CVE-2022-3786)

http://www.openwall.com/lists/oss-security/2022/11/01/24
Web page

oss-security - Re: OpenSSL X.509 Email Address 4-byte Buffer Overflow (CVE-2022-3602), X.509 Email Address Variable Length Buffer Overflow (CVE-2022-3786)

http://www.openwall.com/lists/oss-security/2022/11/01/21
Web page

oss-security - Re: OpenSSL X.509 Email Address 4-byte Buffer Overflow (CVE-2022-3602), X.509 Email Address Variable Length Buffer Overflow (CVE-2022-3786)

http://www.openwall.com/lists/oss-security/2022/11/01/20
Web page

oss-security - Re: OpenSSL X.509 Email Address 4-byte Buffer Overflow (CVE-2022-3602), X.509 Email Address Variable Length Buffer Overflow (CVE-2022-3786)

http://www.openwall.com/lists/oss-security/2022/11/01/19
Web page

oss-security - Re: OpenSSL X.509 Email Address 4-byte Buffer Overflow (CVE-2022-3602), X.509 Email Address Variable Length Buffer Overflow (CVE-2022-3786)

http://www.openwall.com/lists/oss-security/2022/11/01/18
Web page

oss-security - Re: OpenSSL X.509 Email Address 4-byte Buffer Overflow (CVE-2022-3602), X.509 Email Address Variable Length Buffer Overflow (CVE-2022-3786)

http://www.openwall.com/lists/oss-security/2022/11/01/17
Web page

oss-security - Re: OpenSSL X.509 Email Address 4-byte Buffer Overflow (CVE-2022-3602), X.509 Email Address Variable Length Buffer Overflow (CVE-2022-3786)

http://www.openwall.com/lists/oss-security/2022/11/01/16
Web page

oss-security - OpenSSL X.509 Email Address 4-byte Buffer Overflow (CVE-2022-3602), X.509 Email Address Variable Length Buffer Overflow (CVE-2022-3786)

http://www.openwall.com/lists/oss-security/2022/11/01/15
Web page

Packet Storm

http://packetstormsecurity.com/files/169687/OpenSSL-Security-Advisory-20221101.html

Vendor Advisories for CVE-2022-3602(4)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibssl3 (3.0.5-2ubuntu2) @ kinetic2026-10-22ubuntu
redhatubi9/openssl:9.0-252022-11-02redhat
redhatopenssl-1:3.0.1-43.el9_02022-11-01redhat

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

(22 across 14 ecosystems)
Alpine:v3.17(2)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 18.12.1-r0: fixed in 18.12.1-r0
—
openssl—
  • 3.0.0 up to 3.0.7-r0: fixed in 3.0.7-r0
—
Alpine:v3.18(2)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 18.12.1-r0: fixed in 18.12.1-r0
—
openssl—
  • 3.0.0 up to 3.0.7-r0: fixed in 3.0.7-r0
—
Alpine:v3.19(2)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 18.12.1-r0: fixed in 18.12.1-r0
—
openssl—
  • 3.0.0 up to 3.0.7-r0: fixed in 3.0.7-r0
—
Alpine:v3.20(2)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 18.12.1-r0: fixed in 18.12.1-r0
—
openssl—
  • 3.0.0 up to 3.0.7-r0: fixed in 3.0.7-r0
—
Alpine:v3.21(2)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 18.12.1-r0: fixed in 18.12.1-r0
—
openssl—
  • 3.0.0 up to 3.0.7-r0: fixed in 3.0.7-r0
—
Alpine:v3.22(2)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 18.12.1-r0: fixed in 18.12.1-r0
—
openssl—
  • 3.0.0 up to 3.0.7-r0: fixed in 3.0.7-r0
—
Alpine:v3.23(2)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 18.12.1-r0: fixed in 18.12.1-r0
—
openssl—
  • 3.0.0 up to 3.0.7-r0: fixed in 3.0.7-r0
—
Alpine:v3.24(2)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 18.12.1-r0: fixed in 18.12.1-r0
—
openssl—
  • 3.0.0 up to 3.0.7-r0: fixed in 3.0.7-r0
—
Alpine:v3.15(1)
PackageVulnerable rangeFix by version rangeDependents
openssl3—
  • every version up to 3.0.7-r0: fixed in 3.0.7-r0
—
Alpine:v3.16(1)
PackageVulnerable rangeFix by version rangeDependents
openssl3—
  • every version up to 3.0.7-r0: fixed in 3.0.7-r0
—
crates.io(1)
PackageVulnerable rangeFix by version rangeDependents
openssl-src—
  • 300.0.0 up to 300.0.11: fixed in 300.0.11
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 3.0.7-1: fixed in 3.0.7-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 3.0.7-1: fixed in 3.0.7-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 3.0.7-1: fixed in 3.0.7-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 17× in last 7d / 32× 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 80 of 102 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. 20 repeat rows among the latest 100 are merged into the row they repeat. The 22 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-22 23:13 UTCEG score recompute
  2. 2026-10-22 23:13 UTCVendor advisory
  3. 2026-10-21 21:46 UTCEG score recompute
  4. 2026-10-21 21:46 UTCVendor advisory
  5. 2026-10-21 16:29 UTCEPSS rescoreEPSS 91% · 99th percentile
  6. 2026-10-20 19:40 UTCEG score recompute
  7. 2026-10-20 19:40 UTCVendor advisory
  8. 2026-10-19 18:12 UTCEG score recompute
  9. 2026-10-19 18:12 UTCVendor advisory
  10. 2026-10-19 16:28 UTCEPSS rescoreEPSS 91% · 99th percentile
  11. 2026-10-18 16:43 UTCEG score recompute
  12. 2026-10-18 16:43 UTCVendor advisory
  13. 2026-10-18 06:38 UTCEG score recompute
  14. 2026-10-18 06:38 UTCVendor advisory
  15. 2026-10-17 16:29 UTCEPSS rescoreEPSS 91% · 99th percentile
  16. 2026-10-17 05:10 UTCEG score recompute
  17. 2026-10-17 05:10 UTCVendor advisory
  18. 2026-10-16 03:42 UTCEG score recompute
  19. 2026-10-16 03:42 UTCVendor advisory
  20. 2026-10-15 00:35 UTCEG score recompute
  21. 2026-10-15 00:35 UTCVendor advisory
  22. 2026-10-14 16:29 UTCEPSS rescoreEPSS 91% · 99th percentile
  23. 2026-10-13 20:23 UTCEG score recompute
  24. 2026-10-13 20:23 UTCVendor advisory
  25. 2026-10-12 18:21 UTCEG score recompute
Show 55 more
  1. 2026-10-12 18:21 UTCVendor advisory
  2. 2026-10-11 23:15 UTCEG score recompute
  3. 2026-10-06 15:14 UTCEPSS rescoreEPSS 91% · 99th percentile
  4. 2026-09-30 20:10 UTCOSV refresh
  5. 2026-09-30 15:59 UTCEG score recompute
  6. 2026-09-30 15:00 UTCEPSS rescoreEPSS 91% · 99th percentile
  7. 2026-09-24 14:00 UTCEPSS rescoreEPSS 91% · 99th percentile
  8. 2026-09-22 14:45 UTCEPSS rescoreEPSS 91% · 99th percentile
  9. 2026-09-12 02:40 UTCOSV refresh
  10. 2026-09-11 14:50 UTCEPSS rescoreEPSS 91% · 99th percentile
  11. 2026-09-07 15:58 UTCEPSS rescoreEPSS 91% · 99th percentile
  12. 2026-09-06 13:45 UTCEPSS rescoreEPSS 91% · 99th percentile
  13. 2026-09-05 15:25 UTCEPSS rescoreEPSS 91% · 99th percentile
  14. 2026-08-30 19:14 UTCEPSS rescoreEPSS 91% · 99th percentile
  15. 2026-08-28 21:38 UTCEPSS rescoreEPSS 91% · 99th percentile
  16. 2026-08-27 14:22 UTCEPSS rescoreEPSS 91% · 99th percentile
  17. 2026-08-24 14:13 UTCEPSS rescoreEPSS 91% · 99th percentile
  18. 2026-08-24 08:27 UTCOSV refresh
  19. 2026-08-19 17:01 UTCEPSS rescoreEPSS 91% · 99th percentile
  20. 2026-08-18 13:45 UTCEPSS rescoreEPSS 91% · 99th percentile
  21. 2026-08-16 02:11 UTCEPSS rescoreEPSS 91% · 99th percentile
  22. 2026-08-12 13:48 UTCEPSS rescoreEPSS 91% · 99th percentile
  23. 2026-08-08 16:34 UTCEPSS rescoreEPSS 91% · 99th percentile
  24. 2026-08-08 04:49 UTCOSV refresh
  25. 2026-08-07 16:24 UTCEPSS rescoreEPSS 91% · 99th percentile
  26. 2026-07-30 16:25 UTCEPSS rescoreEPSS 91% · 99th percentile
  27. 2026-07-28 15:33 UTCEPSS rescoreEPSS 91% · 99th percentile
  28. 2026-07-24 14:15 UTCEPSS rescoreEPSS 91% · 99th percentile
  29. 2026-07-23 02:12 UTCEG score recompute
  30. 2026-07-22 21:26 UTCEG score recompute▲ 1.50
  31. 2026-07-22 21:26 UTCVendor advisory
  32. 2026-07-22 14:06 UTCEPSS rescoreEPSS 91% · 99th percentile
  33. 2026-07-15 16:56 UTCEPSS rescoreEPSS 91% · 99th percentile
  34. 2026-07-15 01:58 UTCEPSS rescoreEPSS 91% · 99th percentile
  35. 2026-07-13 22:28 UTCEPSS rescoreEPSS 91% · 99th percentile
  36. 2026-07-11 12:52 UTCOSV refresh
  37. 2026-07-06 16:25 UTCEPSS rescoreEPSS 91% · 99th percentile
  38. 2026-07-06 02:21 UTCEPSS rescoreEPSS 90% · 99th percentile
  39. 2026-07-04 06:29 UTCEPSS rescoreEPSS 90% · 99th percentile
  40. 2026-06-28 04:54 UTCEPSS rescoreEPSS 90% · 99th percentile
  41. 2026-06-24 14:03 UTCEPSS rescoreEPSS 90% · 99th percentile
  42. 2026-06-23 21:31 UTCEPSS rescoreEPSS 90% · 99th percentile
  43. 2026-06-22 19:35 UTCOSV refresh
  44. 2026-06-17 17:51 UTCEPSS rescoreEPSS 90% · 99th percentile
  45. 2026-06-15 17:46 UTCEPSS rescoreEPSS 90% · 99th percentile
  46. 2026-06-14 23:15 UTCEPSS rescoreEPSS 84% · 99th percentile
  47. 2026-06-13 22:58 UTCEPSS rescoreEPSS 84% · 99th percentile
  48. 2026-06-12 23:10 UTCEPSS rescoreEPSS 84% · 99th percentile
  49. 2026-06-10 22:17 UTCEPSS rescoreEPSS 84% · 99th percentile
  50. 2026-06-07 15:23 UTCEPSS rescoreEPSS 84% · 99th percentile
  51. 2026-06-06 13:46 UTCEPSS rescoreEPSS 84% · 99th percentile
  52. 2026-06-05 22:45 UTCEPSS rescoreEPSS 84% · 99th percentile
  53. 2026-06-05 09:30 UTCOSV refresh
  54. 2026-06-04 13:11 UTCEPSS rescoreEPSS 84% · 99th percentile
  55. 2026-06-01 13:50 UTCEPSS rescoreEPSS 84% · 99th percentile

Publicly available exploits

(7 references)

Public exploit code is referenced for this CVE (6 GitHub PoCs), as is 1 GitHub checker repository. A GitHub repository named or described as a checker or scanner checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.

  • GitHub PoCcybersecurityworks553/CVE-2022-3602-and-CVE-2022-3786
    Published Nov 7, 2022
    Open source ↗
  • GitHub checkercorelight/CVE-2022-3602
    Published Nov 3, 2022

    Detects attempts at exploitation of CVE-2022-3602, a remote code execution vulnerability in OpenSSL v 3.0.0 through v.3.0.6

    Open source ↗
  • GitHub PoCrbowes-r7/cve-2022-3602-and-cve-2022-3786-openssl-poc
    Published Nov 2, 2022
    Open source ↗
  • GitHub PoCattilaszia/cve-2022-3602
    Published Nov 1, 2022

    cve-2022-3602 poc

    Open source ↗
  • GitHub PoCeatscrayon/CVE-2022-3602-poc
    Published Oct 31, 2022
    Open source ↗
  • GitHub PoCcolmmacc/CVE-2022-3602
    Published Oct 30, 2022
    Open source ↗
  • GitHub PoCNCSC-NL/OpenSSL-2022
    Published Oct 28, 2022

    Operational information regarding CVE-2022-3602 and CVE-2022-3786, two vulnerabilities in OpenSSL 3

    Open source ↗

Related CVEs(same product + same vendor + same CWE)

Same vendor

2 shown

redhat:RHSA-2022:7288 · ubuntu:USN-5710-1

Frequently asked(5)

What is CVE-2022-3602?
CVE-2022-3602 is a critical-severity vulnerability; its CVE record was published on November 1, 2022. A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed the malicious certificate or for the application to continue certificate…
When was CVE-2022-3602 made public?
CVE-2022-3602 was made public on November 1, 2022: 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 November 1, 2022. EchelonGraph's copy of the record carries a last-modified date of April 14, 2026; the record at its source may have been updated since.
Is CVE-2022-3602 actively exploited?
CVE-2022-3602 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 91% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-3602?
CVE-2022-3602 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
How do I remediate CVE-2022-3602?
A fix for CVE-2022-3602 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-3602 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-2022-3602

Explore →

Is Your Infrastructure Affected by CVE-2022-3602?

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

Book a Demo →Browse All CVEs