CVE-2022-0778

HIGHNVD 7.58.7
EchelonGraph scoreHIGH confidence

“▲” 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.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this weekElevated
8.7EG
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 73%
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 73%CVSS: 7.5Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

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

CVSS v3
7.5
EG Score
8.7HIGHhigh confidence
EG Risk
78
EG 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
Patch available.
Web page

[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/
Web page

[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/
Web page

[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/
Web pageMentions a patch (unverified)

[SECURITY] [DLA 2953-1] openssl1.0 security update

https://lists.debian.org/debian-lts-announce/2022/03/msg00024.html
Web pageMentions a patch (unverified)

[SECURITY] [DLA 2952-1] openssl security update

https://lists.debian.org/debian-lts-announce/2022/03/msg00023.html
Web page

[SECURITY] [DSA 5103-1] openssl security update

https://www.debian.org/security/2022/dsa-5103

Patch Availability(22)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuqemu-efi-arm (2022.02-3ubuntu0.22.04.4) @ jammy2026-10-21ubuntu
ubuntunodejs-doc (12.22.9~dfsg-1ubuntu3.1) @ jammy2026-10-21ubuntu
ubuntulibssl1.0.0 (1.0.2g-1ubuntu4.20+esm2) @ xenial2026-10-21ubuntu
ubuntulibssl-doc (1.1.1f-1ubuntu2.12) @ focal2026-10-21ubuntu
redhatcompat-openssl10-1:1.0.2o-4.el8_62022-06-30redhat
redhatrhacm2/management-ingress-rhel8:v2.5.0-142022-06-09redhat
redhatredhat-virtualization-host-0:4.5.0-202205291010_8.62022-06-03redhat
redhatcompat-openssl11-1:1.1.1k-4.el9_02022-06-03redhat
redhatjws5-tomcat-native-0:1.2.30-4.redhat_4.el8jws2022-05-02redhat
redhatopenssl2022-05-02redhat
redhatjbcs-httpd24-openssl-pkcs11-0:0.4.10-26.jbcs.el72022-04-20redhat
redhatredhat-virtualization-host-0:4.3.22-20220330.1.el7_92022-04-07redhat
redhatopenssl-1:1.1.1c-19.el8_22022-03-29redhat
redhatopenssl-1:1.1.1c-5.el8_1.12022-03-29redhat
redhatopenssl-1:1.0.2k-18.el7_62022-03-28redhat
redhatopenssl-1:1.1.1g-16.el8_42022-03-28redhat
redhatopenssl-1:1.0.1e-62.el7_32022-03-28redhat
redhatopenssl-1:1.0.2k-21.el7_72022-03-28redhat
redhatopenssl-0:1.0.1e-60.el6_102022-03-28redhat
redhatopenssl-1:1.0.2k-25.el7_92022-03-28redhat
redhatopenssl-1:1.0.2k-10.el7_42022-03-28redhat
redhatopenssl-1:1.1.1k-6.el8_52022-03-28redhat

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)
PackageVulnerable rangeFix by version rangeDependents
libretls—
  • every version up to 3.3.4-r3: fixed in 3.3.4-r3
—
openssl—
  • 1.0.2 up to 1.1.1n-r0: fixed in 1.1.1n-r0
—
openssl3—
  • every version up to 3.0.2-r0: fixed in 3.0.2-r0
—
Alpine:v3.16(3)
PackageVulnerable rangeFix by version rangeDependents
libretls—
  • every version up to 3.5.1-r0: fixed in 3.5.1-r0
—
openssl—
  • 1.0.2 up to 1.1.1n-r0: fixed in 1.1.1n-r0
—
openssl3—
  • every version up to 3.0.2-r0: fixed in 3.0.2-r0
—
Alpine:v3.14(2)
PackageVulnerable rangeFix by version rangeDependents
libretls—
  • every version up to 3.3.3p1-r3: fixed in 3.3.3p1-r3
—
openssl—
  • 1.0.2 up to 1.1.1n-r0: fixed in 1.1.1n-r0
—
Alpine:v3.17(2)
PackageVulnerable rangeFix by version rangeDependents
libretls—
  • every version up to 3.5.1-r0: fixed in 3.5.1-r0
—
openssl—
  • 1.0.2 up to 3.0.2-r0: fixed in 3.0.2-r0
—
Alpine:v3.18(2)
PackageVulnerable rangeFix by version rangeDependents
libretls—
  • every version up to 3.5.1-r0: fixed in 3.5.1-r0
—
openssl—
  • 1.0.2 up to 3.0.2-r0: fixed in 3.0.2-r0
—
Alpine:v3.19(2)
PackageVulnerable rangeFix by version rangeDependents
libretls—
  • every version up to 3.5.1-r0: fixed in 3.5.1-r0
—
openssl—
  • 1.0.2 up to 3.0.2-r0: fixed in 3.0.2-r0
—
Alpine:v3.20(2)
PackageVulnerable rangeFix by version rangeDependents
libretls—
  • every version up to 3.5.1-r0: fixed in 3.5.1-r0
—
openssl—
  • 1.0.2 up to 3.0.2-r0: fixed in 3.0.2-r0
—
Alpine:v3.21(2)
PackageVulnerable rangeFix by version rangeDependents
libretls—
  • every version up to 3.5.1-r0: fixed in 3.5.1-r0
—
openssl—
  • 1.0.2 up to 3.0.2-r0: fixed in 3.0.2-r0
—
Alpine:v3.22(2)
PackageVulnerable rangeFix by version rangeDependents
libretls—
  • every version up to 3.5.1-r0: fixed in 3.5.1-r0
—
openssl—
  • 1.0.2 up to 3.0.2-r0: fixed in 3.0.2-r0
—
Debian:9(2)
PackageVulnerable rangeFix by version rangeDependents
openssl1.1.0f-3 ... 1.1.0l-1~deb9u4 (18 versions)
  • every version up to 1.1.0l-1~deb9u5: fixed in 1.1.0l-1~deb9u5
—
openssl1.01.0.2l-2 ... 1.0.2u-1~deb9u6 (23 versions)
  • every version up to 1.0.2u-1~deb9u7: fixed in 1.0.2u-1~deb9u7
—
Alpine:v3.12(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 1.1.1n-r0: fixed in 1.1.1n-r0
—
Alpine:v3.13(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 1.1.1n-r0: fixed in 1.1.1n-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 3.0.2-r0: fixed in 3.0.2-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 3.0.2-r0: fixed in 3.0.2-r0
—
crates.io(1)
PackageVulnerable rangeFix by version rangeDependents
openssl-src—
  • 300.0.0 up to 300.0.5: fixed in 300.0.5
  • every version up to 111.18.0: fixed in 111.18.0
  • 0.0.0-0 up to 111.18.0: fixed in 111.18.0
—
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
openssl1.1.1c-1 ... 1.1.1d-0+deb10u7 (8 versions)
  • every version up to 1.1.1d-0+deb10u8: fixed in 1.1.1d-0+deb10u8
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
openssl1.1.1k-1, 1.1.1k-1+deb11u1
  • every version up to 1.1.1k-1+deb11u2: fixed in 1.1.1k-1+deb11u2
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 1.1.1n-1: fixed in 1.1.1n-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 1.1.1n-1: fixed in 1.1.1n-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • every version up to 1.1.1n-1: fixed in 1.1.1n-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(6)

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.

  1. 2026-10-22 16:29 UTCEPSS rescoreEPSS 73% · 99th percentile
  2. 2026-10-21 16:28 UTCEPSS rescoreEPSS 73% · 99th percentile
  3. 2026-10-21 08:25 UTCEG score recompute
  4. 2026-10-21 08:25 UTCVendor advisory
  5. 2026-10-20 16:28 UTCEPSS rescoreEPSS 73% · 99th percentile
  6. 2026-10-19 16:28 UTCEPSS rescoreEPSS 73% · 99th percentile
  7. 2026-10-18 08:48 UTCEG score recompute
  8. 2026-10-15 16:28 UTCEPSS rescoreEPSS 73% · 99th percentile
  9. 2026-10-14 16:29 UTCEPSS rescoreEPSS 73% · 99th percentile
  10. 2026-10-14 13:36 UTCVendor advisory
  11. 2026-10-14 12:33 UTCEG score recompute
  12. 2026-10-14 12:33 UTCVendor advisory
  13. 2026-10-12 19:04 UTCEG score recompute
  14. 2026-10-11 23:30 UTCEG score recompute
  15. 2026-10-11 13:44 UTCEPSS rescoreEPSS 73% · 99th percentile
  16. 2026-10-09 20:04 UTCEPSS rescoreEPSS 73% · 99th percentile
  17. 2026-10-07 23:45 UTCEPSS rescoreEPSS 73% · 99th percentile
  18. 2026-10-07 19:24 UTCOSV refresh
  19. 2026-10-06 15:14 UTCEPSS rescoreEPSS 73% · 99th percentile
  20. 2026-10-02 16:23 UTCEPSS rescoreEPSS 73% · 99th percentile
  21. 2026-09-30 15:46 UTCEG score recompute▲ 0.10
  22. 2026-09-29 15:15 UTCEPSS rescoreEPSS 73% · 99th percentile
  23. 2026-09-26 15:54 UTCEPSS rescoreEPSS 73% · 99th percentile
  24. 2026-09-24 14:00 UTCEPSS rescoreEPSS 73% · 99th percentile
  25. 2026-09-23 13:45 UTCEPSS rescoreEPSS 73% · 99th percentile
Show 62 more
  1. 2026-09-22 14:44 UTCEPSS rescoreEPSS 73% · 99th percentile
  2. 2026-09-21 20:28 UTCEPSS rescoreEPSS 73% · 99th percentile
  3. 2026-09-19 15:38 UTCEPSS rescoreEPSS 73% · 99th percentile
  4. 2026-09-18 19:24 UTCEPSS rescoreEPSS 73% · 99th percentile
  5. 2026-09-18 01:36 UTCOSV refresh
  6. 2026-09-17 19:23 UTCEPSS rescoreEPSS 73% · 99th percentile
  7. 2026-09-16 14:05 UTCEPSS rescoreEPSS 73% · 99th percentile
  8. 2026-09-12 14:57 UTCEPSS rescoreEPSS 73% · 99th percentile
  9. 2026-09-11 14:49 UTCEPSS rescoreEPSS 73% · 99th percentile
  10. 2026-09-11 09:33 UTCEPSS rescoreEPSS 73% · 99th percentile
  11. 2026-09-08 21:57 UTCEPSS rescoreEPSS 73% · 99th percentile
  12. 2026-09-06 13:45 UTCEPSS rescoreEPSS 73% · 99th percentile
  13. 2026-09-05 15:25 UTCEPSS rescoreEPSS 73% · 99th percentile
  14. 2026-09-02 14:09 UTCEPSS rescoreEPSS 73% · 99th percentile
  15. 2026-09-01 13:51 UTCEPSS rescoreEPSS 73% · 99th percentile
  16. 2026-08-30 19:14 UTCEPSS rescoreEPSS 73% · 99th percentile
  17. 2026-08-30 02:43 UTCOSV refresh
  18. 2026-08-30 01:19 UTCEPSS rescoreEPSS 73% · 99th percentile
  19. 2026-08-28 21:38 UTCEPSS rescoreEPSS 73% · 99th percentile
  20. 2026-08-27 14:22 UTCEPSS rescoreEPSS 73% · 99th percentile
  21. 2026-08-26 14:43 UTCEPSS rescoreEPSS 73% · 99th percentile
  22. 2026-08-24 14:13 UTCEPSS rescoreEPSS 73% · 99th percentile
  23. 2026-08-21 23:46 UTCEPSS rescoreEPSS 73% · 99th percentile
  24. 2026-08-20 22:52 UTCEPSS rescoreEPSS 73% · 99th percentile
  25. 2026-08-19 17:01 UTCEPSS rescoreEPSS 73% · 99th percentile
  26. 2026-08-16 14:53 UTCEPSS rescoreEPSS 73% · 99th percentile
  27. 2026-08-16 02:11 UTCEPSS rescoreEPSS 71% · 99th percentile
  28. 2026-08-15 01:27 UTCEPSS rescoreEPSS 71% · 99th percentile
  29. 2026-08-13 21:57 UTCEPSS rescoreEPSS 71% · 99th percentile
  30. 2026-08-13 13:21 UTCOSV refresh
  31. 2026-08-12 13:48 UTCEPSS rescoreEPSS 71% · 99th percentile
  32. 2026-08-11 13:38 UTCEPSS rescoreEPSS 71% · 99th percentile
  33. 2026-08-06 13:44 UTCEPSS rescoreEPSS 71% · 99th percentile
  34. 2026-08-05 19:15 UTCEPSS rescoreEPSS 71% · 99th percentile
  35. 2026-08-04 15:06 UTCEPSS rescoreEPSS 71% · 99th percentile
  36. 2026-08-04 10:34 UTCEPSS rescoreEPSS 71% · 99th percentile
  37. 2026-08-03 10:33 UTCEPSS rescoreEPSS 71% · 99th percentile
  38. 2026-07-30 16:25 UTCEPSS rescoreEPSS 71% · 99th percentile
  39. 2026-07-28 20:21 UTCOSV refresh
  40. 2026-07-28 15:33 UTCEPSS rescoreEPSS 71% · 99th percentile
  41. 2026-07-26 14:52 UTCEPSS rescoreEPSS 71% · 99th percentile
  42. 2026-07-25 14:15 UTCEPSS rescoreEPSS 71% · 99th percentile
  43. 2026-07-24 14:15 UTCEPSS rescoreEPSS 71% · 99th percentile
  44. 2026-07-23 02:07 UTCEG score recompute▲ 1.10
  45. 2026-07-22 22:53 UTCEG score recompute
  46. 2026-07-22 14:06 UTCEPSS rescoreEPSS 71% · 99th percentile
  47. 2026-07-21 15:22 UTCEPSS rescoreEPSS 71% · 99th percentile
  48. 2026-07-20 17:05 UTCEPSS rescoreEPSS 71% · 99th percentile
  49. 2026-07-19 02:27 UTCEPSS rescoreEPSS 71% · 99th percentile
  50. 2026-07-16 17:00 UTCEPSS rescoreEPSS 71% · 99th percentile
  51. 2026-07-15 16:55 UTCEPSS rescoreEPSS 71% · 99th percentile
  52. 2026-07-15 01:58 UTCEPSS rescoreEPSS 71% · 99th percentile
  53. 2026-07-13 06:11 UTCEPSS rescoreEPSS 71% · 99th percentile
  54. 2026-07-11 13:11 UTCOSV refresh
  55. 2026-07-11 08:25 UTCEPSS rescoreEPSS 71% · 99th percentile
  56. 2026-07-09 19:07 UTCEPSS rescoreEPSS 71% · 99th percentile
  57. 2026-07-04 06:29 UTCEPSS rescoreEPSS 71% · 99th percentile
  58. 2026-07-01 15:04 UTCEPSS rescoreEPSS 71% · 99th percentile
  59. 2026-06-27 03:06 UTCEPSS rescoreEPSS 71% · 99th percentile
  60. 2026-06-25 13:48 UTCEPSS rescoreEPSS 71% · 99th percentile
  61. 2026-06-24 14:03 UTCEPSS rescoreEPSS 71% · 99th percentile
  62. 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-0778
    Published Apr 21, 2022

    Proof of concept for CVE-2022-0778 in P12 and PEM format

    Open source ↗
  • GitHub PoCjkakavas/CVE-2022-0778-POC
    Published Apr 18, 2022
    Open source ↗
  • GitHub PoCyywing/cve-2022-0778
    Published Apr 4, 2022
    Open source ↗
  • GitHub PoCdrago-96/CVE-2022-0778
    Published 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 ↗

Frequently asked(5)

What is CVE-2022-0778?
CVE-2022-0778 is a high-severity vulnerability; its CVE record was published on March 15, 2022. The BNmodsqrt() 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…
When was CVE-2022-0778 made public?
CVE-2022-0778 was made public on March 15, 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 March 15, 2022. EchelonGraph's copy of the record carries a last-modified date of October 14, 2026; the record at its source may have been updated since.
Is CVE-2022-0778 actively exploited?
CVE-2022-0778 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 73% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-0778?
CVE-2022-0778 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.7 (HIGH).
How do I remediate CVE-2022-0778?
A fix for CVE-2022-0778 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-0778 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-0778

Explore →

Is Your Infrastructure Affected by CVE-2022-0778?

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