CVE-2022-2053

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 1.1% (63rd 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 a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.1%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

When a POST request comes through AJP and the request exceeds the max-post-size limit (maxEntitySize), Undertow's AjpServerRequestConduit implementation closes a connection without sending any response to the client/proxy. This behavior results in that a front-end proxy marking the backend worker (application server) as an error state and not forward requests to the worker for a while. In mod_cluster, this continues until the next STATUS request (10 seconds intervals) from the application server updates the server state. So, in the worst case, it can result in "All workers are in error state" and mod_cluster responds "503 Service Unavailable" for a while (up to 10 seconds). In mod_proxy_balancer, it does not forward requests to the worker until the "retry" timeout passes. However, luckily, mod_proxy_balancer has "forcerecovery" setting (On by default; this parameter can force the immediate recovery of all workers without considering the retry parameter of the workers if all workers of a balancer are in error state.). So, unlike mod_cluster, mod_proxy_balancer does not result in responding "503 Service Unavailable". An attacker could use this behavior to send a malicious request and trigger server errors, resulting in DoS (denial of service). This flaw was fixed in Undertow 2.2.19.Final, Undertow 2.3.0.Alpha2.

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: 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
1.1%
EPSS %ILE
63rd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or 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 (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

August 5, 2022

Last Modified

November 21, 2024

References (4)

Vendor Advisories for CVE-2022-2053(7)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(7)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhateap7-wildfly-elytron-0:1.10.17-1.Final_redhat_00001.1.el7eap2025-06-25redhat
redhateap7-xml-security-0:2.0.10-2.redhat_00002.1.ep7.el72025-04-28redhat
redhatundertow2022-11-28redhat
redhateap7-undertow-0:2.2.19-1.SP2_redhat_00001.1.el8eap2022-10-05redhat
redhatio.undertow/undertow-core:2.2.19.SP2-redhat-000012022-10-05redhat
redhateap7-undertow-0:2.2.19-1.SP2_redhat_00001.1.el7eap2022-10-05redhat
redhateap7-undertow-0:2.2.19-1.SP2_redhat_00001.1.el9eap2022-10-05redhat

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

(2 across 2 ecosystems)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
undertow1.3.11-1 ... 2.2.8-1 (47 versions)
  • every version up to 2.2.18-1: fixed in 2.2.18-1
—
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
io.undertow:undertow-core2.3.0.Alpha1
  • every version up to 2.2.19.Final: fixed in 2.2.19.Final
  • 2.3.0.Alpha1 up to 2.3.0.Alpha2: fixed in 2.3.0.Alpha2
—

Weakness Classification(1)

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

Data Freshness Timeline

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2022-2053?
CVE-2022-2053 is a high vulnerability published on August 5, 2022. When a POST request comes through AJP and the request exceeds the max-post-size limit (maxEntitySize), Undertow's AjpServerRequestConduit implementation closes a connection without sending any response to the client/proxy. This behavior results in that a front-end proxy marking the backend worker…
When was CVE-2022-2053 disclosed?
CVE-2022-2053 was first published on August 5, 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-2053 actively exploited?
CVE-2022-2053 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.1% probability of exploitation in the next 30 days (63rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-2053?
CVE-2022-2053 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2022-2053?
A fix for CVE-2022-2053 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-2053 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-2053

Explore →

Is Your Infrastructure Affected by CVE-2022-2053?

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

Book a Demo →Browse All CVEs