How this template works
The template uses API selection filters to specify the criteria for selecting the requests to be executed. In this case, the filters include response code, method, response payload, and URL. For example, it selects requests with a response code between 200 and 299, a method of "GET", a response payload containing "<!doctype html>", and extracts the URL as a variable.
The template specifies a single request to be executed. It modifies the URL by appending "/nginx_status" to the extracted URL variable. This is done using the "modify_url" action with a regex_replace operation. The modified URL is then used to make the request.
After executing the request, the template validates the response payload. It checks if the response payload contains the string "Active connections:". If this validation condition is met, the vulnerability is considered present.
Frequently asked questions
What is the purpose of the NGINX Status Disclosure test
How does the NGINX Status Disclosure vulnerability impact the system
What category and subcategory does the NGINX Status Disclosure vulnerability fall under
What are the severity and impact levels of the NGINX Status Disclosure vulnerability
What are the selection filters used for this test
How is the NGINX Status Disclosure test executed