CVE-2022-24666

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 1.4% (70th percentile of EPSS-scored CVEs). 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
7.5EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.4%CVSS: 7.5Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

A program using swift-nio-http2 is vulnerable to a denial of service attack, caused by a network peer sending a specially crafted HTTP/2 frame. This attack affects all swift-nio-http2 versions from 1.0.0 to 1.19.1. This vulnerability is caused by a logical error when parsing a HTTP/2 HEADERS frame where the frame contains priority information without any other data. This logical error caused confusion about the size of the frame, leading to a parsing error. This parsing error immediately crashes the entire process. Sending a HEADERS frame with HTTP/2 priority information does not require any special permission, so any HTTP/2 connection peer may send such a frame. For clients, this means any server to which they connect may launch this attack. For servers, anyone they allow to connect to them may launch such an attack. The attack is low-effort: it takes very little resources to send an appropriately crafted frame. The impact on availability is high: receiving the frame immediately crashes the server, dropping all in-flight connections and causing the service to need to restart. It is straightforward for an attacker to repeatedly send appropriately crafted frames, so attackers require very few resources to achieve a substantial denial of service. The attack does not have any confidentiality or integrity risks in and of itself: swift-nio-http2 is parsing the frame in memory-safe code, so the crash is safe. However, sudden process crashes can lead to violations of invariants in services, so it is possible that this attack can be used to trigger an error condition that has confidentiality or integrity risks. The risk can be mitigated if untrusted peers can be prevented from communicating with the service. This mitigation is not available to many services. The issue is fixed by rewriting the parsing code to correctly handle the condition. The issue was found by automated fuzzing by oss-fuzz.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
39
EG Risk 39/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
1.4%
EPSS %ILE
70th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

February 9, 2022

Last Modified

November 21, 2024

References (2)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 24× 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 168 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2022-24666?
CVE-2022-24666 is a high vulnerability published on February 9, 2022. A program using swift-nio-http2 is vulnerable to a denial of service attack, caused by a network peer sending a specially crafted HTTP/2 frame. This attack affects all swift-nio-http2 versions from 1.0.0 to 1.19.1. This vulnerability is caused by a logical error when parsing a HTTP/2 HEADERS frame…
When was CVE-2022-24666 disclosed?
CVE-2022-24666 was first published on February 9, 2022, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-24666 actively exploited?
CVE-2022-24666 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.4% probability of exploitation in the next 30 days (70th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-24666?
CVE-2022-24666 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2022-24666?
No fix for CVE-2022-24666 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2022-24666

Explore →

Is Your Infrastructure Affected by CVE-2022-24666?

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

Book a Demo →Browse All CVEs