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.
The product does not sufficiently enforce boundaries between the states of different sessions, causing data to be provided to, or used by, the wrong session.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| EAP 8.0.1 | RedHat | * | |
| Red Hat build of Apache Camel 4.4.1 for Spring Boot 3.2 | RedHat | undertow | * |
| Red Hat JBoss Enterprise Application Platform Expansion Pack | RedHat | * | |
| Undertow | Ubuntu | focal | * |
| Undertow | Ubuntu | oracular | * |
| Undertow | Ubuntu | plucky | * |
Data can “bleed” from one session to another through member variables of singleton objects, such as Servlets, and objects from a shared pool. In the case of Servlets, developers sometimes do not understand that, unless a Servlet implements the SingleThreadModel interface, the Servlet is a singleton; there is only one instance of the Servlet, and that single instance is used and re-used to handle multiple requests that are processed simultaneously by different threads. A common result is that developers use Servlet member fields in such a way that one user may inadvertently see another user’s data. In other words, storing user data in Servlet member fields introduces a data access race condition.