This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "Testing for Privilege escalation (OTG-AUTHZ-003)"
m (→Description of the Issue) |
m (→Black Box testing and example) |
||
| Line 20: | Line 20: | ||
== Black Box testing and example == | == Black Box testing and example == | ||
'''Testing for role/privilege manipulation''' <br> | '''Testing for role/privilege manipulation''' <br> | ||
| − | In every portion of the application where a user can create information in the database(a payment, | + | In every portion of the application where a user can create information in the database (e.g., making a payment, adding a contact, or sending a message), to receive information (statement of account, order details, etc.), or delete information (drop users, messages, etc.), it is necessary to record that functionality. The tester should try to access such function as another user in order to verify, for example, if it is possible to access a function that should not be permitted by the user's role/privilege (but might be permitted as another user). |
For example:<br> | For example:<br> | ||
| − | The following HTTP POST | + | The following HTTP POST allows the user that belongs to grp001 to access order #0001: |
POST /path/viewMyOrder.jsp HTTP/1.1 | POST /path/viewMyOrder.jsp HTTP/1.1 | ||
| Line 53: | Line 53: | ||
</tr> | </tr> | ||
| − | What if the tester modifies the value of the variable "profilo" | + | What if the tester modifies the value of the variable "profilo" to “SistemiInf9”? Is it possible to become administrator? |
| − | |||
For example:<br> | For example:<br> | ||
| Line 63: | Line 62: | ||
The server gives an implicit trust to the user. It believes that the user will answer with the above message closing the session. | The server gives an implicit trust to the user. It believes that the user will answer with the above message closing the session. | ||
| − | In this condition, verify that | + | In this condition, verify that it is not possible to escalate privileges, by modifying the parameter values. |
| − | In this particular example modifying the `PVValido` value from '-1' to '0' (no error conditions) it may be possible to authenticate as administrator to the server. | + | In this particular example, by modifying the `PVValido` value from '-1' to '0' (no error conditions), it may be possible to authenticate as administrator to the server. |
<br> | <br> | ||
'''Result Expected:'''<br> | '''Result Expected:'''<br> | ||
| − | The tester should verify execution of successful privilege escalation attempts.<br><br> | + | The tester should verify the execution of successful privilege escalation attempts.<br><br> |
== Gray Box testing and example == | == Gray Box testing and example == | ||
Revision as of 07:53, 19 August 2008
OWASP Testing Guide v3 Table of Contents
This article is part of the OWASP Testing Guide v3. The entire OWASP Testing Guide v3 can be downloaded here.
OWASP at the moment is working at the OWASP Testing Guide v4: you can browse the Guide here
This is a draft of a section of the new Testing Guide v3
Brief Summary
This section describes the issue of escalating privileges from one stage to another. During this phase, the tester should verify that it is not possible for a user to modify his or her privileges/roles inside the application in ways that could allow privilege escalation attacks.
Description of the Issue
Privilege escalation occurs when a user gets access to more resources or functionality than they are normally allowed and such elevation/changes should have been prevented by the application. This is usually caused by a flaw in the application. The result is that the application performs actions with more privileges than those intended by the developer or system administrator.
The degree of escalation depends on which privileges the attacker is authorized to possess and which privileges can be obtained in a successful exploit. For example, a programming error that allows a user to gain extra privilege after successful authentication limits the degree of escalation because the user is already authorized to hold some privilege. Likewise, a remote attacker gaining superuser privilege without any authentication presents a greater degree of escalation.
Usually, we refer to vertical escalation when it is possible to access resources granted to more privileged accounts (e.g., acquiring administrative privileges for the application), and to horizontal escalation when it is possible to access resources granted to a similarly configured account (e.g., in an online banking application, accessing information related to a different user).
Black Box testing and example
Testing for role/privilege manipulation
In every portion of the application where a user can create information in the database (e.g., making a payment, adding a contact, or sending a message), to receive information (statement of account, order details, etc.), or delete information (drop users, messages, etc.), it is necessary to record that functionality. The tester should try to access such function as another user in order to verify, for example, if it is possible to access a function that should not be permitted by the user's role/privilege (but might be permitted as another user).
For example:
The following HTTP POST allows the user that belongs to grp001 to access order #0001:
POST /path/viewMyOrder.jsp HTTP/1.1 Host: www.example.com [other HTTP Headers]
gruppoID=grp001&ordineID=0001
Verify if a user that does not belong to grp001 can modify the value of the parameters ‘gruppoID’ and ‘ordineID’ to gain access to that privileged data.
For example:
The following server's answer shows a hidden field in the HTML returned to the user after a successful authentication.
HTTP/1.1 200 OK Server: Netscape-Enterprise/6.0 Date: Wed, 1 Apr 2006 13:51:20 GMT Set-Cookie: USER=aW78ryrGrTWs4MnOd32Fs51yDqp; path=/; domain=www.example.com Set-Cookie: SESSION=k+KmKeHXTgDi1J5fT7Zz; path=/; domain= www.example.com Cache-Control: no-cache Pragma: No-cache Content-length: 247 Content-Type: text/html Expires: Thu, 01 Jan 1970 00:00:00 GMT Connection: close <form name=“autoriz" method="POST" action = “visual.jsp"> <input type="hidden" name="profilo" value="SistemiInf1"> <body onload="document.forms.autoriz.submit()"> </td> </tr>
What if the tester modifies the value of the variable "profilo" to “SistemiInf9”? Is it possible to become administrator?
For example:
In an environment in which the server sends an error message contained as value in a specific parameter in a set of answer's codes, as the following:
@0`1`3`3``0`UC`1`Status`OK`SEC`5`1`0`ResultSet`0`PVValido`-1`0`0` Notifications`0`0`3`Command Manager`0`0`0` StateToolsBar`0`0`0` StateExecToolBar`0`0`0`FlagsToolBar`0
The server gives an implicit trust to the user. It believes that the user will answer with the above message closing the session. In this condition, verify that it is not possible to escalate privileges, by modifying the parameter values. In this particular example, by modifying the `PVValido` value from '-1' to '0' (no error conditions), it may be possible to authenticate as administrator to the server.
Result Expected:
The tester should verify the execution of successful privilege escalation attempts.
Gray Box testing and example
Testing for Topic X vulnerabilities:
...
Result Expected:
...
References
Whitepapers
...
Tools
- OWASP WebScarab
...
