CVE-2022-2053
- Source
- https://nvd.nist.gov/vuln/detail/CVE-2022-2053
- Import Source
- https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2022-2053.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2022-2053
- Aliases
- Related
- Published
- 2022-08-05T16:15:11Z
- Modified
- 2024-10-12T08:54:37.691471Z
- Severity
-
- 7.5 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H CVSS Calculator
- Summary
- [none]
- Details
-
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 modcluster, 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 modcluster responds "503 Service Unavailable" for a while (up to 10 seconds). In modproxybalancer, it does not forward requests to the worker until the "retry" timeout passes. However, luckily, modproxybalancer 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 modcluster, modproxy_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.
- References
Affected packages
Git / github.com/undertow-io/undertow
Affected ranges
- Type
- GIT
- Repo
- https://github.com/undertow-io/undertow
- Events
-
Introduced0 Unknown introduced commit / All previous commits are affectedFixed