HTTP Method Fuzzing Scan

The HTTP Method Fuzzing scan finds weaknesses in the service by generating the semi-random input through HTTP methods.

Typically, an attacker tries to send random requests through various HTTP methods in order to provoke some kind of unexpected behavior or obtain useful system information. The HTTP Method Fuzzing scan checks how your service handles such requests by sending multiple unexpected requests.

If the scan does not reveal any information about possible vulnerabilities, it passes successfully.

If the scan has Failed, that means your service responds to undocumented methods, indicating instabilities or vulnerability to iterative HTTP method requests. This causes security problems or reveal sensitive data.

• This scan is applicable to REST test steps or REST requests.

• To use this scan, you need a ReadyAPI Test  license. If you do not have it, request it on our web site or start a trial.

The HTTP Method Fuzzing scan generates a multitude of requests by using HTTP methods not included in the API definition.

It uses assertions to validate each response and check if it includes any information about potential vulnerabilities.

If a response passes all assertions, PASS will be logged for that response. If any assertion fails, FAIL will be logged.

If you have not applied any assertions to the scan, Unknown will be logged for the response.

• Default assertion
  Sensitive Information Exposure – Verifies that your server does not reveal any information that is useful for attacks (such as stack traces if the server crashes).

The HTTP Method Fuzzing scan attempts to access the service through various HTTP methods.

By default, any methods included in the definition are considered safe.

To exclude other methods you consider safe from the scan, uncheck them in the list.

Use the following options to configure the scan Strategy:

• API Testing Dojo – Security Vulnerability Testing

• Fuzzing on the OWASP website