Access Control Bypass by changing request method to HEAD
Many authentication mechanisms only limit access to the most common HTTP methods, thus allowing unauthorized access to restricted resources by other HTTP methods.
Unnecessary HTTP Methods (UHM)
How this template works
The template uses the "response_code" filter to select APIs that have a response code equal to 302. This filter ensures that only APIs with a specific response code are targeted for testing.
The template specifies a single request to be executed. It modifies the HTTP method to HEAD and removes the authentication header from the request. This is done to test if the server is vulnerable to access control bypass by changing the request method to HEAD.
The template validates the response code of the executed request. It checks if the response code is greater than or equal to 200 and less than 300, indicating a successful response. This validation ensures that the server responded with a 2XX success code, indicating a potential access control bypass vulnerability.
Frequently asked questions
What is the purpose of the HEAD_METHOD_TEST in this array
How does the access control bypass vulnerability occur in this test
What is the impact of the access control bypass vulnerability in this test
What is the severity level assigned to this vulnerability
What are the tags associated with this vulnerability
Can you provide references for further reading on this vulnerability