Access Control Bypass by changing request method to an arbitrary value
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 "TestMethod" and removes the authentication header. This allows the test to simulate an access control bypass by changing the request method to an arbitrary value.
The template validates the response code of the executed request. It checks that the response code is greater than or equal to 200 and less than 300, indicating a successful response. This 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 "Access Control Bypass by changing request method to an arbitrary value" test
How does the test simulate an access control bypass
What is the impact of a successful access control bypass in this test
What is the severity level assigned to this vulnerability
What are the recommended references for further information on this vulnerability
What are the tags associated with this vulnerability