CVE-2022-2053: Undertow core Denial of Service Vulnerability
HIGHCVE-2022-2053 is a HIGH (CVSS 7.5) denial of service vulnerability (CWE-400: Uncontrolled Resource Consumption) affecting Undertow core libraries in the Maven ecosystem. The issue involves undertow vulnerable to dos via large ajp request. Remediation is available by upgrading affected packages to version 2.2.19.Final, 2.3.0.Alpha2.
CVE-2022-2053 at a Glance
Security Impact
CVSS: 7.5
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).
How to Fix CVE-2022-2053
To remediate this vulnerability, upgrade all affected Undertow core dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
<dependency>
<groupId>io.undertow</groupId>
<artifactId>undertow-core</artifactId>
<version>2.2.19.Final</version>
</dependency><dependency>
<groupId>io.undertow</groupId>
<artifactId>undertow-core</artifactId>
<version>2.3.0.Alpha2</version>
</dependency>Run the following command in your project directory to verify that all resolved dependencies use the patched release:
mvn dependency:tree -Dincludes=io.undertowHow to Check if You Are Affected
To determine whether your Java application is affected by CVE-2022-2053, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:tree -Dincludes=io.undertowAnalyze the terminal output to locate any version of Undertow core in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.2.19.Final), your application is affected.
Note: The mvn dependency:tree -Dincludes=io.undertow command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-400: Uncontrolled Resource Consumption, where the product does not properly control the allocation and maintenance of a limited resource. In Undertow core, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2022-2053 Affected Undertow core Versions
2 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
io.undertow:undertow-core
|
Maven |
< 2.2.19.Final
|
2.2.19.Final
|
|
io.undertow:undertow-core
|
Maven |
≥ 2.3.0.Alpha1
< 2.3.0.Alpha2
All 1 versions
2.3.0.Alpha1
|
2.3.0.Alpha2
|
References
Frequently Asked Questions
What is CVE-2022-2053?
Which Undertow core versions are affected?
What version fixes CVE-2022-2053?
Is undertow-core affected?
What is the CVSS score of CVE-2022-2053?
What CWE is associated with CVE-2022-2053?
How can I check Maven dependencies for CVE-2022-2053?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-95rf-557x-44g5",
"modified" : "2022-08-18T18:49:44Z",
"published" : "2022-08-06T00:00:46Z",
"aliases" : [ "CVE-2022-2053" ],
"summary" : "Undertow vulnerable to Dos via Large AJP request",
"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 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.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Maven",
"name" : "io.undertow:undertow-core"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "2.2.19.Final"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Maven",
"name" : "io.undertow:undertow-core"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "2.3.0.Alpha1"
}, {
"fixed" : "2.3.0.Alpha2"
} ]
} ],
"versions" : [ "2.3.0.Alpha1" ]
} ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2022-2053"
}, {
"type" : "WEB",
"url" : "https://github.com/undertow-io/undertow/pull/1350"
}, {
"type" : "WEB",
"url" : "https://bugzilla.redhat.com/show_bug.cgi?id=2095862&comment#0"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/undertow-io/undertow"
}, {
"type" : "WEB",
"url" : "https://issues.redhat.com/browse/UNDERTOW-2133"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-400" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2022-08-18T18:49:44Z",
"nvd_published_at" : "2022-08-05T16:15:00Z"
}
}