published 12 Mar 2018 · updated 17 Sep 2024
The IIS/ISAPI specific code in the Apache Tomcat JK ISAPI Connector 1.2.0 to 1.2.42 that normalised the requested path before matching it…
5.5MediumEPSS 47%
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 47%. No fixed version is recorded.
The IIS/ISAPI specific code in the Apache Tomcat JK ISAPI Connector 1.2.0 to 1.2.42 that normalised the requested path before matching it to the URI-worker map did not handle some edge cases correctly. If only a sub-set of the URLs supported by Tomcat were exposed via IIS, then it was possible for a specially constructed request to expose application functionality through the reverse proxy that was not intended for clients accessing Tomcat via the reverse proxy.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Apache Software Foundation | =Apache Tomcat JK ISAPI Connector 1.2.0 to 1.2.42 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket