Undertow: url-encoded request path information can be broken on ajp-listener
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 2%. Fixed in 2.2.33.Final and 2.3.14.
A vulnerability was found in Undertow, where URL-encoded request paths can be mishandled during concurrent requests on the AJP listener. This issue arises because the same buffer is used to decode the paths for multiple requests simultaneously, leading to incorrect path information being processed. As a result, the server may attempt to access the wrong path, causing errors such as "404 Not Found" or other application failures. This flaw can potentially lead to a denial of service, as legitimate resources become inaccessible due to the path mix-up.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Red Hat | Build of Apache Camel | ||
| Red Hat | Build of Keycloak | ||
| Red Hat | Data Grid | ||
| Red Hat | EAP | ||
| Red Hat | Fuse | ||
| Red Hat | Integration Camel K | ||
| Red Hat | JBoss | ||
| Red Hat | Process Automation | ||
| Red Hat | Single Sign-On | ||
| Red Hat | build of Apache Camel - HawtIO | ||
| Red Hat | build of Apache Camel for Spring Boot | ||
| <2.2.33.Final, >=2.3.0.Alpha1 <2.3.14 | 2.2.33.Final, 2.3.14 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in JBoss, strongest first
Embed
A live severity badge for an advisory, README or ticket