Tuesday, 21 October 2014

How to Test HTTP Protocol

HTTP refers to Hyper Text Transfer Protocol; its motion the number of method’s that can be used to performs activity on the web server. Several of these methods are developed to help of developers in deploying or testing of the HTTP applications. These HTTP methods can be used for un-trustful purposes, if the web server is misconfigured. Additionally, Cross Site Tracing, a form of cross site scripting writing using the server's HTTP TRACE methods, is examined.
When GET & POST are through away the most common methods that used to retrieve information provided through a web server, the HTTP allows several other methods. 
The following methods of the HTTP such as:
  • Ø  HEAD
  • Ø  GET
  • Ø  POST
  • Ø  TRACE
  • Ø  PUT
Some methods can potentially pretense a security risk for the web application, as they allow an attacker’s to modify the files and stored on the web server or, in some scenario’s, thieve the login information of lawful users. More particularly, the methods that should be disabling are the following:

1.       PUT:
In this method, it allows a client’s to upload the new files on web server. An attacker can avail it through uploading malicious files.

2.       DELETE:
This method allows; a customer to delete files on the web server. An attacker’s can exploits as a very simple & direct way to de-face a web site and to fell a DoS (Denial of service) attack.

3.       CONNECT:
 This method allows to a client to use of web server as a proxy.

4.       TRACE:
This method, really assumed harm less, which can be used to hill an attacks known as  “Cross Site Tracing”.

How to test?

To perform testing, the tester required some way to point out which HTTP methods are supported through the web server i.e. being examined. The “OPTIONS HTTP” methods endow the tester with the most direct & effective path to do that.

Test to XST probable

The TRACE method, while obviously harmless, can be triumphantly leveraged in some scenario’s to steal lawful users' credentials. This attack technique was discovered in 2003, in this attempt to bypass the HTTP Only tag that Microsoft proposed in Internet Explorer to save cookies from being accessed through JavaScript.

Testing for arbitrary HTTP methods

Find page and to visit that has a security constraints such that it would redirect to log in page and forces to a log in straightly.
If the tester feels that system is permeable to this issue, attacks to exploits the issue more:
·         JEFF /admin/changePw.php?member=myAdmin&passwd=foo123&confirm=foo123
·         FOOBAR /admin/createUser.php?member=myAdmin
·         CATS /admin/groupEdit.php?group=Admins&member=myAdmin&action=add

Testing for HEAD access control bypass
Finds a page and to visit that has a security constraints such that redirects the login page and forces a login straightly.
If the testers think that the system is permeable to this issue, attacks to exploits the issues more:
·         HEAD /admin/changePw.php?member=myAdmin&passwd=foo123&confirm=foo123
·         HEAD /admin/createUser.php?member=myAdmin
·         HEAD /admin/groupEdit.php?group=Admins&member=myAdmin&action=add

No comments:

Post a comment

Bookmark Us

Delicious Digg Facebook Favorites More Stumbleupon Twitter