---
title: "CVE-2022-2053\n    | Ubuntu"
description: Ubuntu is an open source software operating system that runs from the
  desktop, to the cloud, to all your internet connected things.
url: https://ubuntu.com/security/CVE-2022-2053?format=md
keywords: index, follow
---

# CVE-2022-2053

Publication date 5 August 2022

Last updated 11 July 2025

---

Ubuntu priority

**Medium**

[Why this priority?](https://ubuntu.com/security/cves/about#priority )

## Cvss 3 Severity Score

**7.5 · High**

[Score breakdown](https://ubuntu.com/security/CVE-2022-2053?format=md#impact-score)

Toggle side navigation

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

## Status

Show unmaintained releases

| Package | Ubuntu Release | Status |
| --- | --- | --- |
| undertow | 26.04 LTS resolute | Needs evaluation |
| 25.10 questing | Ignored end of life, was needs-triage |
| 25.04 plucky | Ignored end of life, was needs-triage |
| 24.10 oracular | Ignored end of life, was needs-triage |
| 24.04 LTS noble | Needs evaluation |
| 23.10 mantic | Not in release |
| 23.04 lunar | Not in release |
| 22.10 kinetic | Ignored end of life, was needs-triage |
| 22.04 LTS jammy | Needs evaluation |
| 21.10 impish | Ignored end of life |
| 20.04 LTS focal | Needs evaluation |
| 18.04 LTS bionic | Needs evaluation |
| 16.04 LTS xenial | Needs evaluation |

---

* [How can I get the fixes?](https://ubuntu.com/security/cves/about#security)
* [What do statuses mean?](https://ubuntu.com/security/cves/about#statuses)

## Severity score breakdown

CVSS version:
CVSS v3.0

**Base score**

7.5 · High

* Base metrics

  | Parameter | Value |
  | --- | --- |
  | Attack vector | Network |
  | Attack complexity | Low |
  | Privileges required | None |
  | User interaction | None |
  | Scope | Unchanged |
  | Confidentiality impact | None |
  | Integrity impact | None |
  | Availability impact | High |
* Scores

  | Parameter | Value |
  | --- | --- |
  | Base score | 7.5 · High |
  | Exploitability score | - |
  | Impact score | - |

**Vector:** CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

## References

* [MITRE](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2053)
* [NVD](https://nvd.nist.gov/vuln/detail/CVE-2022-2053)
* [Launchpad](https://launchpad.net/bugs/cve/CVE-2022-2053)
* [Debian](https://security-tracker.debian.org/tracker/CVE-2022-2053)

### Other references

* <https://bugzilla.redhat.com/show_bug.cgi?id=2095862>
* <https://www.cve.org/CVERecord?id=CVE-2022-2053>