CVE-2018-1323: Infoleak
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.
Other sources
The ISAPI redirector code in Apache Tomcat JK Connector before version 1.2.43 does not properly handle HTTP request paths in certain edge cases. A remote attacker could exploit this by sending a crafted request to expose application functionality through the reverse proxy.
External References:
http://tomcat.apache.org/security-jk.html#FixedinApacheTomcatJKConnector1.2.43
Upstream Patch:
http://svn.apache.org/viewvc?view=revision&revision=1825658
— Red Hat
Affected Software
Event History
Frequently Asked Questions
What is the vulnerability ID for this vulnerability?
The vulnerability ID for this vulnerability is CVE-2018-1323.
What is the severity of CVE-2018-1323?
The severity of CVE-2018-1323 is high with a severity value of 7.5.
What is the affected software for CVE-2018-1323?
The affected software for CVE-2018-1323 is Apache Tomcat JK ISAPI Connector version 1.2.0 to 1.2.42.
How can I fix CVE-2018-1323?
To fix CVE-2018-1323, update the Apache Tomcat JK ISAPI Connector to version 1.2.43.
Where can I find more information about CVE-2018-1323?
More information about CVE-2018-1323 can be found at the following references: http://tomcat.apache.org/security-jk.html#Fixed_in_Apache_Tomcat_JK_Connector_1.2.43, http://svn.apache.org/viewvc?view=revision&revision=1825658, https://access.redhat.com/errata/RHSA-2018:1843.