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
Configurations
History
No history.
Information
Published : 2018-03-12 16:29
Updated : 2024-02-04 19:46
NVD link : CVE-2018-1323
Mitre link : CVE-2018-1323
CVE.ORG link : CVE-2018-1323
JSON object : View
Products Affected
apache
- tomcat_jk_connector