Alphan Yavas

**Name of the Vulnerable Software and Affected Versions** MicroStrategy versions prior to 11.1.3 **Description** The issue is related to reflected XSS in the Microstrategy Library. **Recommendations** For versions prior to 11.1.3, update to version 11.1.3 or later to resolve the issue.

**Name of the Vulnerable Software and Affected Versions** Microsoft Exchange Server versions prior to Rollup 18 for Microsoft Exchange Server 2010 SP3 **Description** The issue concerns a Server-Side Request Forgery (SSRF) vulnerability. It can be exploited via the `username` parameter in the "/owa/auth/logon.aspx" API endpoint, which is part of the OWA (Outlook Web Access) login page. **Recommendations** For versions prior to Rollup 18 for Microsoft Exchange Server 2010 SP3, apply Rollup 18 to resolve the issue. As a temporary workaround, consider restricting access to the "/owa/auth/logon.aspx" API endpoint to minimize the risk of exploitation. Avoid using the `username` parameter in the affected API endpoint until the issue is resolved.

**Name of the Vulnerable Software and Affected Versions** Microsoft ADFS versions prior to 4.0 on Windows Server 2016 and previous **Description** The issue concerns a Server-Side Request Forgery (SSRF) vulnerability. It can be exploited via the `txtBoxEmail` parameter in the "/adfs/ls" API endpoint. **Recommendations** For Microsoft ADFS versions prior to 4.0 on Windows Server 2016 and previous, as a temporary workaround, consider restricting access to the `/adfs/ls` API endpoint to minimize the risk of exploitation. Avoid using the `txtBoxEmail` parameter in the affected API endpoint until the issue is resolved.

**Name of the Vulnerable Software and Affected Versions** Apache Tomcat JK ISAPI Connector versions 1.2.0 through 1.2.42 **Description** The issue concerns the normalization of requested paths in the Apache Tomcat JK ISAPI Connector. It did not handle certain edge cases correctly, potentially allowing a specially constructed request to expose application functionality through the reverse proxy that was not intended for clients accessing Tomcat via the reverse proxy. **Recommendations** For Apache Tomcat JK ISAPI Connector versions 1.2.0 through 1.2.42, consider updating to a version that addresses this issue, as the current version may allow unintended exposure of application functionality. At the moment, there is no information about a newer version that contains a fix for this vulnerability.