Products

Solutions

Resources

Search for API Security Tests

/

/

Access Control Bypass by changing request method to HEAD

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)

"It may be possible to bypass authentication or authorization on this endpoint by changing the HTTP method to HEAD. The original request was replayed by removing victim's <b>auth</b> token. The server responded with 2XX success codes.<br>" "<b>Background:</b> An access control vulnerability can arise if the server does not properly enforce authorization checks for certain resources when the HEAD method is used. This vulnerability can allow an attacker to bypass access controls and gain unauthorized access to restricted resources. The access bypass control by changing the HTTP method to HEAD occurs when an attacker modifies the HTTP request method from a restricted method (e.g., POST) to the HEAD method. By doing so, the attacker aims to exploit the server's vulnerability in handling authorization checks for the HEAD method, which may differ from other methods."

"It may be possible to bypass authentication or authorization on this endpoint by changing the HTTP method to HEAD. The original request was replayed by removing victim's <b>auth</b> token. The server responded with 2XX success codes.<br>" "<b>Background:</b> An access control vulnerability can arise if the server does not properly enforce authorization checks for certain resources when the HEAD method is used. This vulnerability can allow an attacker to bypass access controls and gain unauthorized access to restricted resources. The access bypass control by changing the HTTP method to HEAD occurs when an attacker modifies the HTTP request method from a restricted method (e.g., POST) to the HEAD method. By doing so, the attacker aims to exploit the server's vulnerability in handling authorization checks for the HEAD method, which may differ from other methods."

Impact of the vulnerability

Impact of the vulnerability

Broken User authentication is a serious vulnerability. Attackers can gain control to other user's accounts in the system, read their personal data, and perform sensitive actions on their behalf, like money transactions and sending personal messages.

Broken User authentication is a serious vulnerability. Attackers can gain control to other user's accounts in the system, read their personal data, and perform sensitive actions on their behalf, like money transactions and sending personal messages.

How this template works

APIs Selection

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.

Execute request

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.

Validation

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

Loved by security teams!

Loved by security teams!

Product Hunt Badge

"We are absolutely thrilled with the testing feature of Akto. We have used it on our graphQL endpoints and it performs flawlessly identifying common API security issues. It's truly a game-changer and we highly recommend Akto to anyone looking to effortlessly secure their API endpoints. With a user-friendly interface, it's the perfect solution for anyone looking to embrace custom rules with context to reduce false positives."

Loom Company logo

Security team,

Loom

"We are absolutely thrilled with the testing feature of Akto. We have used it on our graphQL endpoints and it performs flawlessly identifying common API security issues. It's truly a game-changer and we highly recommend Akto to anyone looking to effortlessly secure their API endpoints. With a user-friendly interface, it's the perfect solution for anyone looking to embrace custom rules with context to reduce false positives."

Loom Company logo

Security team,

Loom

"The text editor in Akto is absolutely remarkable. Its user-friendly YAML format strikes the perfect balance between simplicity and power. With intuitive features like 'API selection filter', 'Execute', Validate' creating test rules becomes incredibly easy. Akto's test editor is a game-changer, enabling seamless creation of highly personalized and effective tests that could meet the needs of any modern day organization. "

Rippling Company logo

Security team,

Rippling

Suggest API security tests

Suggest API security tests

We're actively building the test library. Suggest a test! If we like your suggestion, you will see it in the library in few days.

We're actively building the test library. Suggest a test! If we like your suggestion, you will see it in the library in few days.