/
HTTP OPTIONS Vulnerability – IIS

HTTP OPTIONS Vulnerability – IIS

Written by Spencer Malmad



Overview

Using Nexpose we have identified a number of vulnerabilities and this document will show out to remediate the HTTP OPTIONS METHOD vulnerability.

For further information see https://www.owasp.org/index.php/Test_HTTP_Methods_(OTG-CONFIG-006)



Disable HTTP OPTIONS Method in IIS

The following Steps disable the HTTP OPTIONS Method on Windows Server 2008r2, 2012, 2012R2 as well as 2016.

Effectively the following setting is made in the global web.config file:

C:\inetpub\wwwroot\web.config:



<?xml version="1.0" encoding="UTF-8"?>

<configuration>

   <system.webServer>

       <security>

           <requestFiltering>

               <verbs>

                   <add verb="OPTIONS" allowed="false" />

               </verbs>

           </requestFiltering>

       </security>

   </system.webServer>

</configuration>



STEPS:

Logged in with administrative rights to the Windows Server:

Launch Start -> Run -> enter Inetmgr, hit <enter>.

You will be prompted with the UAC:  Click “Yes”.

The following will display:

Navigate to “<IIS Servername> -> “Request Filtering”

The following will display:

Open Tab “HTTP VERBS”.  The following will appear:

Right Click in white space and choose “Deny Verb” from the drop down.

Enter the text “OPTIONS”, Click “OK”.








Related content

Windows Web Servers Should be Configured to Use Secure Communication Protocols
Windows Web Servers Should be Configured to Use Secure Communication Protocols
More like this
HTTP OPTIONS Vulnerability – Apache
HTTP OPTIONS Vulnerability – Apache
More like this
TLS IIS Weak Chiphers – Windows Server 2008r2-2016
TLS IIS Weak Chiphers – Windows Server 2008r2-2016
More like this
Ensure That 'HTTP Version' is the Latest, if Used to Run the Web App
Ensure That 'HTTP Version' is the Latest, if Used to Run the Web App
More like this
Vulnerabilities in Security Configuration on your Machines Should be Remediated
Vulnerabilities in Security Configuration on your Machines Should be Remediated
More like this
Web Application Should Only be Accessible Over HTTPS
Web Application Should Only be Accessible Over HTTPS
More like this