The BN_mod_sqrt() function, which computes a modular square root, contains a bug that can cause it to loop forever for non-prime moduli. Internally this function is used when parsing certificates that contain elliptic curve public keys in compressed form or explicit elliptic curve parameters with a base point encoded in compressed form. It is possible to trigger the infinite loop by crafting a certificate that has invalid explicit curve parameters. Since certificate parsing happens prior to verification of the certificate signature, any process that parses an externally supplied certificate may thus be subject to a denial of service attack. The infinite loop can also be reached when parsing crafted private keys as they can contain explicit elliptic curve parameters. Thus vulnerable situations include: - TLS clients consuming server certificates - TLS servers consuming client certificates - Hosting providers taking certificates or private keys from customers - Certificate authorities parsing certification requests from subscribers - Anything else which parses ASN.1 elliptic curve parameters Also any other applications that use the BN_mod_sqrt() where the attacker can control the parameter values are vulnerable to this DoS issue. In the OpenSSL 1.0.2 version the public key is not parsed during initial parsing of the certificate which makes it slightly harder to trigger the infinite loop. However any operation which requires the public key from the certificate will trigger the infinite loop. In particular the attacker can use a self-signed certificate to trigger the loop during verification of the certificate signature. This issue affects OpenSSL versions 1.0.2, 1.1.1 and 3.0. It was addressed in the releases of 1.1.1n and 3.0.2 on the 15th March 2022. Fixed in OpenSSL 3.0.2 (Affected 3.0.0,3.0.1). Fixed in OpenSSL 1.1.1n (Affected 1.1.1-1.1.1m). Fixed in OpenSSL 1.0.2zd (Affected 1.0.2-1.0.2zc).
CVE-2022-0778
“▲” beside the score: it is higher than NVD's CVSS score.
Score elevated to 8.7 because EPSS predicted 73% 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.
- High exploitation likelihood — EPSS 73%
- Public exploit or proof-of-concept code is available
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 8.7HIGHhigh confidence
- EG Risk
- 78EG Risk 78/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.Exploitation73% × 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
- 73%
- 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 (8.7): severity, escalated by confirmed exploitation. This CVE's 8.7 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
- 73% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-20). 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
March 15, 2022
Last Modified
October 14, 2026
Advisory Details (7)
Auto-updated Oct 14, 2026[SECURITY] Fedora 36 Update: openssl1.1-1.1.1n-1.fc36 - package-announce - Fedora mailing-lists
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/W6K3PR542DXWLEFFMFIDMME4CWMHJRMG/[SECURITY] Fedora 34 Update: openssl-1.1.1n-1.fc34 - package-announce - Fedora mailing-lists
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/323SNN6ZX7PRJJWP2BUAFLPUAE42XWLZ/[SECURITY] Fedora 35 Update: openssl-1.1.1n-1.fc35 - package-announce - Fedora mailing-lists
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/GDB3GQVJPXJE7X5C5JN6JAA4XUDWD6E6/[SECURITY] [DLA 2953-1] openssl1.0 security update
https://lists.debian.org/debian-lts-announce/2022/03/msg00024.html[SECURITY] [DLA 2952-1] openssl security update
https://lists.debian.org/debian-lts-announce/2022/03/msg00023.html[SECURITY] [DSA 5103-1] openssl security update
https://www.debian.org/security/2022/dsa-5103Vendor Advisories for CVE-2022-0778(20)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- CVE-2022-0778Microsoft Security Response Center (MSRC)
CVE-2022-0778
- RHSA-2022:5326Red Hat Product SecurityLow
Red Hat Security Advisory: compat-openssl10 security update
- RHSA-2022:4956Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Advanced Cluster Management 2.5 security updates, images, and bug fixes
- RHSA-2022:4899Red Hat Product SecurityHigh
Red Hat Security Advisory: compat-openssl11 security and bug fix update
- RHSA-2022:4896Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Virtualization security, bug fix, and enhancement update [ovirt-4.5.0]
- RHSA-2022:1519Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat JBoss Web Server 5.6.2 Security Update
- RHSA-2022:1520Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat JBoss Web Server 5.6.2 Security Update
- RHSA-2022:1476Red Hat Product SecurityMedium
Red Hat Security Advisory: Red Hat Advanced Cluster Management 2.4.3 security updates and bug fixes
- +12 more
Patch Availability(22)
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
(32 across 20 ecosystems)
Alpine:v3.15(3)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| libretls | — |
| — |
| openssl | — |
| — |
| openssl3 | — |
| — |
Alpine:v3.16(3)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| libretls | — |
| — |
| openssl | — |
| — |
| openssl3 | — |
| — |
Alpine:v3.14(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| libretls | — |
| — |
| openssl | — |
| — |
Alpine:v3.17(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| libretls | — |
| — |
| openssl | — |
| — |
Alpine:v3.18(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| libretls | — |
| — |
| openssl | — |
| — |
Alpine:v3.19(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| libretls | — |
| — |
| openssl | — |
| — |
Alpine:v3.20(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| libretls | — |
| — |
| openssl | — |
| — |
Alpine:v3.21(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| libretls | — |
| — |
| openssl | — |
| — |
Alpine:v3.22(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| libretls | — |
| — |
| openssl | — |
| — |
Debian:9(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssl | 1.1.0f-3 ... 1.1.0l-1~deb9u4 (18 versions) |
| — |
| openssl1.0 | 1.0.2l-2 ... 1.0.2u-1~deb9u6 (23 versions) |
| — |
Alpine:v3.12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssl | — |
| — |
Alpine:v3.13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssl | — |
| — |
Alpine:v3.23(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssl | — |
| — |
Alpine:v3.24(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssl | — |
| — |
crates.io(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssl-src | — |
| — |
Debian:10(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssl | 1.1.1c-1 ... 1.1.1d-0+deb10u7 (8 versions) |
| — |
Debian:11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssl | 1.1.1k-1, 1.1.1k-1+deb11u1 |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssl | — |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssl | — |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| openssl | — |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(6)
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 7× in last 7d / 24× 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 87 of 169 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. 13 repeat rows among the latest 100 are merged into the row they repeat. The 82 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-22 16:29 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-10-21 16:28 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-10-21 08:25 UTCEG score recompute
- 2026-10-21 08:25 UTCVendor advisory
- 2026-10-20 16:28 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-10-19 16:28 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-10-18 08:48 UTCEG score recompute
- 2026-10-15 16:28 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-10-14 16:29 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-10-14 13:36 UTCVendor advisory
- 2026-10-14 12:33 UTCEG score recompute
- 2026-10-14 12:33 UTCVendor advisory
- 2026-10-12 19:04 UTCEG score recompute
- 2026-10-11 23:30 UTCEG score recompute
- 2026-10-11 13:44 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-10-09 20:04 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-10-07 23:45 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-10-07 19:24 UTCOSV refresh
- 2026-10-06 15:14 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-10-02 16:23 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-09-30 15:46 UTCEG score recompute▲ 0.10
- 2026-09-29 15:15 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-09-26 15:54 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-09-24 14:00 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-09-23 13:45 UTCEPSS rescoreEPSS 73% · 99th percentile
Show 62 moreShow fewer
- 2026-09-22 14:44 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-09-21 20:28 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-09-19 15:38 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-09-18 19:24 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-09-18 01:36 UTCOSV refresh
- 2026-09-17 19:23 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-09-16 14:05 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-09-12 14:57 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-09-11 14:49 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-09-11 09:33 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-09-08 21:57 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-09-06 13:45 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-09-05 15:25 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-09-02 14:09 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-09-01 13:51 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-08-30 19:14 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-08-30 02:43 UTCOSV refresh
- 2026-08-30 01:19 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-08-28 21:38 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-08-27 14:22 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-08-26 14:43 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-08-24 14:13 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-08-21 23:46 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-08-20 22:52 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-08-19 17:01 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-08-16 14:53 UTCEPSS rescoreEPSS 73% · 99th percentile
- 2026-08-16 02:11 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-08-15 01:27 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-08-13 21:57 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-08-13 13:21 UTCOSV refresh
- 2026-08-12 13:48 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-08-11 13:38 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-08-06 13:44 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-08-05 19:15 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-08-04 15:06 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-08-04 10:34 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-08-03 10:33 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-07-30 16:25 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-07-28 20:21 UTCOSV refresh
- 2026-07-28 15:33 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-07-26 14:52 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-07-25 14:15 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-07-24 14:15 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-07-23 02:07 UTCEG score recompute▲ 1.10
- 2026-07-22 22:53 UTCEG score recompute
- 2026-07-22 14:06 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-07-21 15:22 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-07-20 17:05 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-07-19 02:27 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-07-16 17:00 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-07-15 16:55 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-07-15 01:58 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-07-13 06:11 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-07-11 13:11 UTCOSV refresh
- 2026-07-11 08:25 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-07-09 19:07 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-07-04 06:29 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-07-01 15:04 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-06-27 03:06 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-06-25 13:48 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-06-24 14:03 UTCEPSS rescoreEPSS 71% · 99th percentile
- 2026-06-23 21:31 UTCEPSS rescoreEPSS 71% · 99th percentile
Publicly available exploits
(4 references)Public exploit code is referenced for this CVE (4 GitHub PoCs). Defenders should treat patch urgency accordingly.
- GitHub PoC0xUhaw/CVE-2022-0778Published Apr 21, 2022
Proof of concept for CVE-2022-0778 in P12 and PEM format
Open source ↗ - Open source ↗GitHub PoCjkakavas/CVE-2022-0778-POCPublished Apr 18, 2022
- Open source ↗GitHub PoCyywing/cve-2022-0778Published Apr 4, 2022
- GitHub PoCdrago-96/CVE-2022-0778Published Mar 15, 2022
Proof of concept for CVE-2022-0778, which triggers an infinite loop in parsing X.509 certificates due to a bug in BN_mod_sqrt
Open source ↗
Related CVEs(same product + same vendor + same CWE)
Same product
10 shownAlpine:v3.12:openssl
- CVE-2021-23840NVD 7.5EG 8.1EPSS p99HIGH
- CVE-2021-3712NVD 7.4EG 8.0EPSS p99HIGH
- CVE-2021-23841EG 5.9EPSS p94MEDIUM
- CVE-2020-1971EG 5.9EPSS p94MEDIUM
- CVE-2019-1551EG 5.3EPSS p97MEDIUM
- CVE-2019-1547EG 4.7MEDIUM
- CVE-2019-1563EG 3.7EPSS p90LOW
- CVE-2018-0734EG 5.9EPSS p96MEDIUM
- CVE-2021-3711EG 9.8EPSS p100CRITICAL
- CVE-2020-1967NVD 7.5EG 8.1EPSS p99HIGH
Same vendor
10 shownredhat:RHSA-2022:1389 · redhat:RHSA-2022:1263 · ubuntu:USN-6457-1
Frequently asked(5)
What is CVE-2022-0778?
When was CVE-2022-0778 made public?
Is CVE-2022-0778 actively exploited?
What is the CVSS score of CVE-2022-0778?
How do I remediate CVE-2022-0778?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-0778
Is Your Infrastructure Affected by CVE-2022-0778?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.