Undertow's url-encoded request path information can be broken on ajp-listener
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.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2024-6162US | — | — | ||
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 i… | ||||
references
External citations — patches, advisories, analysis.
- https://access.redhat.com/errata/RHSA-2024:1194WEB
- https://access.redhat.com/errata/RHSA-2024:4386WEB
- https://access.redhat.com/errata/RHSA-2024:4884WEB
- https://access.redhat.com/security/cve/CVE-2024-6162WEB
- https://bugzilla.redhat.com/show_bug.cgi?id=2293069WEB
- https://github.com/undertow-io/undertowPACKAGE
- https://github.com/undertow-io/undertow/commit/90f202ada89b6d9883beed0f1fe10c99d470d9a8WEB
- https://github.com/undertow-io/undertow/commit/a28ac53076e2fa532266d25e0c0b1a01d0e9d2cfWEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan