HTTP methods
Last updated
Was this helpful?
Last updated
Was this helpful?
Some websites filter access to resources but fail at filtering out all HTTP methods. When an attacker tries to access a resource with different methods (GET, POST, HEAD, etc.) to bypass the access control, this is called HTTP verb tampering.
Some HTTP methods can be used for malicious purposes: PUT, DELETE, etc. The HTTP methods abuse is not aimed at gaining access to a specific page like verb tampering but more like what methods are accepted by the server and how can an attacker profit from those.
Testing for HTTP verb tampering and method abuse can be done with .
A manual HTTP request with the OPTIONS method can also be used to enumerate what methods are supported. This works if the OPTIONS methods is allowed in the first place.
PUT methodThe PUT method can be used to upload arbitrary files. Some directories have different rights, it can be useful to test the method on a wide range of directories.
Abusing the PUT method also applies to CVE-2017-12615: When running Apache Tomcat 7.0.0 to 7.0.79 on Windows with HTTP PUTs enabled (e.g. via setting the read-only initialization parameter of the Default to false) it was possible to upload a JSP file to the server via a specially crafted request. This JSP could then be requested and any code it contained would be executed by the server.
Exploitation of this vulnerability can be achieved manually by creating a .jsp file and by uploading it to the target server.
If the upload is successful, the following JSP webshell () can then be uploaded to attempt at execute arbitrary commands on the remote server.