Search for packages
| purl | pkg:maven/io.undertow/undertow-core@2.3.0 |
| Tags | Ghost |
| Next non-vulnerable version | 2.3.20.Final |
| Latest non-vulnerable version | 2.4.0.Beta1 |
| Risk | 4.5 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-4v1f-kt5y-w7d1
Aliases: CVE-2022-2764 |
Undertow: DoS can be achieved as Undertow server waits for the LAST_CHUNK forever for EJB invocations |
Affected by 6 other vulnerabilities. |
|
VCID-93ut-2de3-ckc5
Aliases: CVE-2022-1319 |
undertow: Double AJP response for 400 from EAP 7 results in CPING failures |
Affected by 6 other vulnerabilities. |
|
VCID-jz3d-vvfb-jfbw
Aliases: CVE-2022-4492 GHSA-pfcc-3g6r-8rg8 |
Undertow client not checking server identity presented by server certificate in https connections The undertow client is not checking the server identity presented by the server certificate in https connections. This should be performed by default in https and in http/2. |
Affected by 5 other vulnerabilities. |
|
VCID-usz2-tufg-k7gz
Aliases: CVE-2023-1108 GHSA-m4mm-pg93-fv78 |
Undertow denial of service vulnerability A flaw was found in undertow. This issue makes achieving a denial of service possible due to an unexpected handshake status updated in SslConduit, where the loop never terminates. |
Affected by 5 other vulnerabilities. |
|
VCID-xftw-raz7-b7e1
Aliases: CVE-2022-2053 GHSA-95rf-557x-44g5 |
Undertow vulnerable to Dos via Large AJP request 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. |
Affected by 6 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| This package is not known to fix vulnerabilities. | ||