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.
References
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: apache
Published: 2018-03-12T00:00:00
Updated: 2020-02-13T16:10:17
Reserved: 2017-12-07T00:00:00
Link: CVE-2018-1323
JSON object: View
NVD Information
Status : Modified
Published: 2018-03-12T16:29:00.300
Modified: 2023-11-07T02:55:58.030
Link: CVE-2018-1323
JSON object: View
Redhat Information
No data.