The vulnerability is with a Cross-Site Request Forgery attack in which a user is tricked into visiting a malicious webpage that is crafted specifically for the target Exchange organization. This could allow the attacker to perform actions on behalf of the user, such as adding new inbox rules and to change other OWA user options.
To reduce the risk for this attack, you can disable the Options panel by using UrlScan. You can use UrlScan to block known parts of URLs that are used to access the Options pages in OWA.
Note The Options pages is where most of the user level settings and rules in OWA reside.
UrlScan is an IIS feature which uses an ISAPI filter to process http requests sent to the OWA website. Every request first passes through this filter before the request is processed by Exchange Server. There are predictable patterns within the query string portion and the body of every request transmitted to the Options panel. The predictable patterns can be used to selectively deny the requests.
Note UrlScan will deny every request for accessing or to update Options items or the rules in OWA. These include requests from legitimate users within the organization.
To download UrlScan 32bit, visit the following Microsoft website:
How to disable the Options panel in Exchange Server 2007
You have to set up UrlScan as a filter for the OWA website. For more information about how to set up UrlScan, visit the following website:
After you install UrlScan, the ISAPI filter on your computer resembles the following:
The UrlScan.ini File Setting
Set the UrlScan.ini file with the settings shown underneath. All the strings specified in “DenyOWAOptions” are searched in the URL and query string. If they occur, the request is denied by IIS.
After you install UrlScan and configure the settings, users can log on to OWA as the following picture shows:
However, when a user clicks on the Options button on the upper-right corner, the user receives the following 403 error message:
The UrlScan install directory also has a log file that contains the details of which requests were blocked and the reason for blocking. For example, you may see some information resembles the following information in the log file:
2010-07-16 23:50:23 126.96.36.199 1 GET /owa/?ae=Options&opturl=Messaging Rejected rule+'BlockOptionsInOWA'+triggered query+string - ae=options
The administrator can use standard IIS log parsing tools, such as LogParser, to obtain more information and statistics about the logs. For more information about how to query these logs, visit the following website: