mend-for-github-com[bot]
commented
6 months ago :heavy_check_mark: This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.
CVE-2022-2053 - High Severity Vulnerability
undertow-core-1.4.20.Final.jar
Undertow
Library home page: http://www.jboss.org/
Path to dependency file: /tools/nibrs-fbi-service/pom.xml
Path to vulnerable library: /tools/nibrs-fbi-service/target/nibrs-fbi-service-1.0.0/WEB-INF/lib/undertow-core-1.4.20.Final.jar,/home/wss-scanner/.m2/repository/io/undertow/undertow-core/1.4.20.Final/undertow-core-1.4.20.Final.jar
Dependency Hierarchy: - :x: **undertow-core-1.4.20.Final.jar** (Vulnerable Library)
undertow-core-1.4.25.Final.jar
Undertow
Library home page: http://www.jboss.org/
Path to dependency file: /tools/nibrs-route/pom.xml
Path to vulnerable library: /tools/nibrs-route/target/nibrs-route-1.0.0/WEB-INF/lib/undertow-core-1.4.25.Final.jar,/home/wss-scanner/.m2/repository/io/undertow/undertow-core/1.4.25.Final/undertow-core-1.4.25.Final.jar
Dependency Hierarchy: - :x: **undertow-core-1.4.25.Final.jar** (Vulnerable Library)
Found in HEAD commit: e33ecd45d71662f63121c238ca1c416a6631a650
Found in base branch: master
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.
Publish Date: 2022-08-05
URL: CVE-2022-2053
Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High
For more information on CVSS3 Scores, click here.Type: Upgrade version
Origin: https://github.com/advisories/GHSA-95rf-557x-44g5
Release Date: 2022-08-05
Fix Resolution: io.undertow:undertow-core:2.2.19.Final
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.