Search for packages
| purl | pkg:maven/io.undertow/undertow-core@2.2.9.Final |
| Next non-vulnerable version | 2.3.20.Final |
| Latest non-vulnerable version | 2.4.0.Beta1 |
| Risk | 4.0 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-14ff-vn3t-vyhy
Aliases: CVE-2021-3690 GHSA-fj7c-vg2v-ccrm GMS-2022-2964 |
Undertow vulnerable to memory exhaustion due to buffer leak Buffer leak on incoming WebSocket PONG message(s) in Undertow before 2.0.40 and 2.2.10 can lead to memory exhaustion and allow a denial of service. |
Affected by 0 other vulnerabilities. Affected by 13 other vulnerabilities. |
|
VCID-1vrj-chs2-d3ab
Aliases: CVE-2023-1973 GHSA-97cq-f4jm-mv8h |
Undertow Denial of Service vulnerability A flaw was found in Undertow package. Using the FormAuthenticationMechanism, a malicious user could trigger a Denial of Service by sending crafted requests, leading the server to an OutofMemory error, exhausting the server's memory. |
Affected by 3 other vulnerabilities. Affected by 2 other vulnerabilities. |
|
VCID-2cv5-9v62-kfbm
Aliases: CVE-2024-1459 GHSA-v76w-3ph8-vm66 |
Undertow Path Traversal vulnerability A path traversal vulnerability was found in Undertow. This issue may allow a remote attacker to append a specially-crafted sequence to an HTTP request for an application deployed to JBoss EAP, which may permit access to privileged or restricted files and directories. |
Affected by 4 other vulnerabilities. Affected by 3 other vulnerabilities. |
|
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 7 other vulnerabilities. Affected by 6 other vulnerabilities. |
|
VCID-5585-a76n-zubf
Aliases: CVE-2023-5379 |
Allocation of Resources Without Limits or Throttling A flaw was found in Undertow. When an AJP request is sent that exceeds the max-header-size attribute in ajp-listener, JBoss EAP is marked in an error state by mod_cluster in httpd, causing JBoss EAP to close the TCP connection without returning an AJP response. This happens because mod_proxy_cluster marks the JBoss EAP instance as an error worker when the TCP connection is closed from the backend after sending the AJP request without receiving an AJP response, and stops forwarding. This issue could allow a malicious user could to repeatedly send requests that exceed the max-header-size, causing a Denial of Service (DoS). |
Affected by 4 other vulnerabilities. |
|
VCID-62gn-nwup-8uat
Aliases: CVE-2022-1259 |
undertow: potential security issue in flow control over HTTP/2 may lead to DOS(incomplete fix for CVE-2021-3629) |
Affected by 7 other vulnerabilities. |
|
VCID-7yc7-e35f-8uhj
Aliases: CVE-2023-3223 GHSA-65h2-wf7m-q2v8 |
Uncontrolled Resource Consumption A flaw was found in undertow. Servlets annotated with @MultipartConfig may cause an OutOfMemoryError due to large multipart content. This may allow unauthorized users to cause remote Denial of Service (DoS) attack. If the server uses fileSizeThreshold to limit the file size, it's possible to bypass the limit by setting the file name in the request to null. |
Affected by 5 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 0 other vulnerabilities. Affected by 10 other vulnerabilities. Affected by 7 other vulnerabilities. Affected by 6 other vulnerabilities. |
|
VCID-cf5j-2dz8-7bbu
Aliases: CVE-2021-3859 GHSA-339q-62wm-c39w GMS-2022-2963 |
Undertow vulnerable to Denial of Service (DoS) attacks Undertow client side invocation timeout raised when calling over HTTP2, this vulnerability can allow attacker to carry out denial of service (DoS) attacks in versions less than 2.2.15 Final. |
Affected by 0 other vulnerabilities. Affected by 11 other vulnerabilities. |
|
VCID-ns3p-22xg-q3bz
Aliases: CVE-2025-9784 GHSA-95h4-w6j8-2rp8 |
Undertow MadeYouReset HTTP/2 DDoS Vulnerability A flaw was found in Undertow where malformed client requests can trigger server-side stream resets without triggering abuse counters. This issue, referred to as the "MadeYouReset" attack, allows malicious clients to induce excessive server workload by repeatedly causing server-side stream aborts. While not a protocol bug, this highlights a common implementation weakness that can be exploited to cause a denial of service (DoS). |
Affected by 1 other vulnerability. Affected by 0 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. 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 10 other vulnerabilities. Affected by 3 other vulnerabilities. Affected by 5 other vulnerabilities. Affected by 6 other vulnerabilities. |
|
VCID-xme8-usmd-vqg3
Aliases: CVE-2024-7885 GHSA-9623-mqmm-5rcf |
Undertow vulnerable to Race Condition A vulnerability was found in Undertow where the ProxyProtocolReadListener reuses the same StringBuilder instance across multiple requests. This issue occurs when the parseProxyProtocolV1 method processes multiple requests on the same HTTP connection. As a result, different requests may share the same StringBuilder instance, potentially leading to information leakage between requests or responses. In some cases, a value from a previous request or response may be erroneously reused, which could lead to unintended data exposure. This issue primarily results in errors and connection termination but creates a risk of data leakage in multi-request environments. |
Affected by 2 other vulnerabilities. Affected by 1 other vulnerability. |
|
VCID-yn69-8upm-7yc2
Aliases: CVE-2021-3629 GHSA-rf6q-vx79-mjxr |
Undertow Uncontrolled Resource Consumption A flaw was found in Undertow. A potential security issue in flow control handling by the browser over HTTP/2 may potentially cause overhead or a denial of service in the server. The highest threat from this vulnerability is availability. This flaw affects Undertow versions prior to 2.0.40.Final and prior to 2.2.11.Final. |
Affected by 12 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| VCID-gsr8-1dea-effx | undertow Race Condition vulnerability A flaw was found in undertow. The HTTP2SourceChannel fails to write the final frame under some circumstances, resulting in a denial of service. The highest threat from this vulnerability is availability. This flaw affects Undertow versions prior to 2.0.35.SP1, prior to 2.2.6.SP1, prior to 2.2.7.SP1, prior to 2.0.36.SP1, prior to 2.2.9.Final and prior to 2.0.39.Final. |
CVE-2021-3597
GHSA-mfhv-gwf8-4m88 |