7.5

CVE-2022-2053: redhat integration_camel_k Uncontrolled Resource Consumption

Modified
AliasesUBUNTU-CVE-2022-2053DEBIAN-CVE-2022-2053GHSA-95rf-557x-44g5
Published 05-08-2022Last modified 03-08-2024

Vulnerability summary

CVE-2022-2053 is a high (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in redhat integration_camel_k. EPSS estimates a 1.09% chance of exploitation in the next 30 days, higher than 65.4% of scored vulnerabilities.

Priority
Prioritisesevere

Severe, CVSS 7.5 (NVD); no exploitation reported by the 5 checked sources; EPSS 1% (FIRST, 03-11-2026)

Source freshness unavailable

How is this decided?
CVSS score
7.5/10
010
High · v3.1 (NVD)
EPSS score
1.09%
0%100%
Low · +0.03 pp in 30 days
KEVNot listedNot listed by any tracked catalog.
RansomwareNot flaggedNo ransomware use recorded.
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 5

Timeline

  1. 05-08-2022
    PublishedVulnerability first disclosed.
  2. 03-08-2024
    Last modifiedVulnerability information updated.

Description

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 metrics

4 scores · 4 sources · 1 version

EPSS trend

Probability

1.09%

Chance of exploitation in the next 30 days

Percentile

65%

Versus all other CVEs

30-day change

Increase +0.03 pp

From 1.06% on 04-10-2026

04-10-202603-11-2026

Known exploited

Compare KEV catalogs
CISA KEV

Not in the CISA KEV catalog.

ENISA CNW

Not in the ENISA CNW catalog.

CIRCL

Not in the CIRCL catalog.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Version check

Known conditions: network-reachable, no authentication, no user interaction (CVSS vector). Other conditions: not stated in public data.

Redhat3 products
Debian1 product
  • undertow< 2.2.18-1
Io.undertow1 product
  • undertow-core< 2.2.19.Final | ≥ 2.3.0.Alpha1, < 2.3.0.Alpha2
Ubuntu1 product
  • undertowAll versions (No fix recorded)

4 vendors · 6 products

References

9 links