- CheckMates
- :
- Products
- :
- General Topics
- :
- Re: OPTIONS Method enabled vulnerability detected ...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
OPTIONS Method enabled vulnerability detected on gateways WAN IP.
Anyone have any idea to close "OPTIONS Method enabled" VA on checkpoint firewall. Our VAPT team scans the firewall WAN IP and detected this "application supports the OPTIONS HTTP method due to web server misconfiguration."
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Options is regarded safer as it is read only, different to post or put - and web servers today do operate on https only. So why this is a vulnerability, please give sources / references !
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Encourage you to share further details via a support ticket for review.
See also: sk69160
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you all for the updates, It was false a positive.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We also had this identified as vulnerability from external pentest:
Extended HTTP Methods Allowed
By issuing an "OPTIONS" Web Request to the remote Web Server (HTTP OPTIONS Method), we have managed to identify the extended HTTP Methods supported.
We have managed to identify that the remote Web Server supports the following HTTP Methods:
Based on the response to an OPTIONS request :
- HTTP methods GET HEAD OPTIONS POST are allowed on :
/sslvpn/Login
Some of the extended HTTP methods that are configured on the remote web server can potentially pose a security risk for the web application(s), as they provide the opportunity to an attacker to modify the files stored on the web server or disclose sensitive information such as the base names and extensions used by the webserver.
Any idea why it's enabled and how we can disable?
