CVE-2022-0778

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 70.6%, top 1% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
7.5
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 71%
CISA-KEV: Not listedEPSS: 71%CVSS: 7.5Exploit: NoneExposed: 0

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
7.5(medium)
EPSS
99.3%
KEV
Not listed

Published

March 15, 2022

Last Modified

May 22, 2026

References (63)

Patch Availability(22)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuqemu-efi-riscv64 (2025.02-3ubuntu2.2) @ plucky2026-05-22ubuntu
ubuntulibssl1.0.0 (1.0.2g-1ubuntu4.20+esm2) @ xenial2026-05-22ubuntu
ubuntulibssl-doc (1.1.1f-1ubuntu2.12) @ focal2026-05-22ubuntu
ubuntunodejs-doc (12.22.9~dfsg-1ubuntu3.1) @ jammy2026-05-22ubuntu
redhatcompat-openssl10-1:1.0.2o-4.el8_62022-06-30redhat
redhatrhacm2/management-ingress-rhel8:v2.5.0-142022-06-09redhat
redhatcompat-openssl11-1:1.1.1k-4.el9_02022-06-03redhat
redhatredhat-virtualization-host-0:4.5.0-202205291010_8.62022-06-03redhat
redhatopenssl2022-05-02redhat
redhatjws5-tomcat-native-0:1.2.30-4.redhat_4.el8jws2022-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-5.el8_1.12022-03-29redhat
redhatopenssl-1:1.1.1c-19.el8_22022-03-29redhat
redhatopenssl-1:1.0.1e-62.el7_32022-03-28redhat
redhatopenssl-1:1.1.1k-6.el8_52022-03-28redhat
redhatopenssl-1:1.1.1g-16.el8_42022-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.0.2k-18.el7_62022-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

(1 across 1 ecosystem)
crates.io(1)
PackageVulnerable rangeFixed inDependents
openssl-src300.0.5

Weakness Classification(1)

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

Additional Vendor Advisories

(15)

Data Freshness Timeline

(refreshed 9× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 110 total refreshes for this CVE.

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

Publicly available exploits

(4 references)

Working exploit code is in the public domain (4 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoC0xUhaw/CVE-2022-0778
    First seen Apr 21, 2022

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

    Open source ↗
  • GitHub PoCjkakavas/CVE-2022-0778-POC
    First seen Apr 18, 2022
    Open source ↗
  • GitHub PoCyywing/cve-2022-0778
    First seen Apr 4, 2022
    Open source ↗
  • GitHub PoCdrago-96/CVE-2022-0778
    First seen 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 vulnerability 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 disclosed?
CVE-2022-0778 was first published in the National Vulnerability Database on March 15, 2022, with the most recent update on May 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-0778 actively exploited?
CVE-2022-0778 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2022-0778?
CVE-2022-0778 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2022-0778?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-0778, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.