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.
Advisories

No advisories yet.

Fixes

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

Wed, 16 Jul 2025 13:45:00 +0000

Type Values Removed Values Added
Metrics epss

{'score': 0.56727}

epss

{'score': 0.58383}


cve-icon MITRE

Status: PUBLISHED

Assigner: apache

Published:

Updated: 2024-09-17T02:16:54.351Z

Reserved: 2017-12-07T00:00:00

Link: CVE-2018-1323

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

Published: 2018-03-12T16:29:00.300

Modified: 2024-11-21T03:59:37.630

Link: CVE-2018-1323

cve-icon Redhat

Severity : Important

Publid Date: 2018-03-13T00:00:00Z

Links: CVE-2018-1323 - Bugzilla

cve-icon OpenCVE Enrichment

No data.