How this template works
APIs Selection
The template includes a filter for the response code, specifically selecting APIs where the response code is greater than or equal to 200 and less than 300. This filter ensures that only APIs with successful responses are considered for further testing.
Execute request
The template specifies a single request to be executed. In this case, the request includes a step to remove the authentication header. This step simulates an attacker removing the authentication token to exploit the broken authentication vulnerability.
Validation
The template includes a validation step to check the response code of the executed request. Similar to the API selection filters, the validation ensures that the response code is within the range of 200 to 300, indicating a successful response. This confirms that the vulnerability was successfully exploited and the server responded with a 2XX success code.
Frequently asked questions
Q: What is the purpose of the "remove_auth_header" parameter in the test request
Q: How does the test determine if the authentication mechanism is broken
Q: What is the impact of the "Broken User Authentication" vulnerability
Q: What are the recommended references for understanding and addressing broken authentication vulnerabilities
Q: What is the severity level assigned to the "Broken User Authentication (BUA)" category
Q: What are the tags associated with this test
"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. "
Security team,
Rippling
