Learn how HTTP response headers can reveal server version information, understand the security risks, and discover best practices to prevent server information disclosure and reduce attack surface.
Server Version Disclosure (SVD)
How this template works
APIs Selection
The template uses API selection filters to specify the criteria for selecting the APIs to be tested. In this case, it filters the APIs based on the response code, ensuring that it falls within the range of 200 to 299. It also extracts the URL from the response and assigns it to the variable "urlVar".
Execute request
The template uses the "execute" section to define the type of request to be executed. In this case, it is a single request. The request is modified by replacing the URL with the value of the "urlVar" variable.
Validation
The template uses the "validate" section to define the validation criteria for the response. It checks that the response code falls within the range of 200 to 299 and also validates the response headers. Specifically, it checks if the "Server" header exists and its value matches the specified regex pattern, which captures the server software version number.
Frequently asked questions
What is the purpose of the "Server Version Exposed Via Response Header" test
How does the test modify the original request
What is the significance of the "Server" header in the server response
What is the potential impact of server version disclosure vulnerabilities
What category and subcategory does this test fall under
What are some references for further information on 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
