CVE-2022-3252

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.8% (55th 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 mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%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.

Improper detection of complete HTTP body decompression SwiftNIO Extras provides a pair of helpers for transparently decompressing received HTTP request or response bodies. These two objects (HTTPRequestDecompressor and HTTPResponseDecompressor) both failed to detect when the decompressed body was considered complete. If trailing junk data was appended to the HTTP message body, the code would repeatedly attempt to decompress this data and fail. This would lead to an infinite loop making no forward progress, leading to livelock of the system and denial-of-service. This issue can be triggered by any attacker capable of sending a compressed HTTP message. Most commonly this is HTTP servers, as compressed HTTP messages cannot be negotiated for HTTP requests, but it is possible that users have configured decompression for HTTP requests as well. The attack is low effort, and likely to be reached without requiring any privilege or system access. The impact on availability is high: the process immediately becomes unavailable but does not immediately crash, meaning that it is possible for the process to remain in this state until an administrator intervenes or an automated circuit breaker fires. If left unchecked this issue will very slowly exhaust memory resources due to repeated buffer allocation, but the buffers are not written to and so it is possible that the processes will not terminate for quite some time. This risk can be mitigated by removing transparent HTTP message decompression. The issue is fixed by correctly detecting the termination of the compressed body as reported by zlib and refusing to decompress further data. The issue was found by Vojtech Rylko (https://github.com/vojtarylko) and reported publicly on GitHub.

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

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 (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability30% × 15%
EchelonGraph's default before algorithm v3.4: CISA had not published Automatable for this CVE.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines at low or medium mission impact and sooner than that at high, and watch for a fix.
EPSS PROB
0.8%
EPSS %ILE
56th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track 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 within your standard update timelines at low or medium mission impact and sooner than that at high, and watch for a 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). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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

Published

September 21, 2022

Last Modified

November 21, 2024

References (1)

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 25× 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 176 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 89 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2022-3252?
CVE-2022-3252 is a high-severity vulnerability; its CVE record was published on September 21, 2022. Improper detection of complete HTTP body decompression SwiftNIO Extras provides a pair of helpers for transparently decompressing received HTTP request or response bodies. These two objects (HTTPRequestDecompressor and HTTPResponseDecompressor) both failed to detect when the decompressed body was…
When was the CVE record for CVE-2022-3252 published?
The CVE record for CVE-2022-3252 was published on September 21, 2022. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 21, 2024; the record at its source may have been updated since.
Is CVE-2022-3252 actively exploited?
CVE-2022-3252 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (56th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-3252?
CVE-2022-3252 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2022-3252?
No fix for CVE-2022-3252 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2022-3252?

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

Book a Demo →Browse All CVEs