Staging Environment: Content and features may be unstable or change without notice.
Search for packages
Package details: pkg:rpm/redhat/eap7-undertow@2.2.19-1.SP2_redhat_00001.1?arch=el7eap
purl pkg:rpm/redhat/eap7-undertow@2.2.19-1.SP2_redhat_00001.1?arch=el7eap
Next non-vulnerable version None.
Latest non-vulnerable version None.
Risk 4.0
Vulnerabilities affecting this package (2)
Vulnerability Summary Fixed by
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) There are no reported fixed by versions.
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. There are no reported fixed by versions.
Vulnerabilities fixed by this package (0)
Vulnerability Summary Aliases
This package is not known to fix vulnerabilities.

Date Actor Action Vulnerability Source VulnerableCode Version
2026-04-01T13:59:02.084903+00:00 RedHat Importer Affected by VCID-62gn-nwup-8uat https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2022-1259.json 38.0.0
2026-04-01T13:58:10.912886+00:00 RedHat Importer Affected by VCID-xftw-raz7-b7e1 https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2022-2053.json 38.0.0