Difference between revisions of "Parameter Delimiter"
|Line 6:||Line 6:|
This attack is based on manipulation of
This attack is based on manipulation of used by web application input vectors, in order to cause unexpected behaviors like access control and authorization bypass, information disclosure, among others.
Revision as of 12:02, 14 September 2008
ASDR Table of Contents
This attack is based on the manipulation of parameter delimiters used by web application input vectors, in order to cause unexpected behaviors like access control and authorization bypass, and information disclosure, among others.
In order to illustrate this vulnerability, it’ll be used a vulnerability found on Poster V2, a posting system based on PHP programming language.
This application has a dangerous vulnerability that allows inserting data into user fields (username, password, email address and privileges) in “mem.php” file, which is responsible for managing application user.
An example of the file “mem.php”, where user Jose has admin privileges and Alice user access:
<? Joseemail@example.com|admin| Alicefirstname.lastname@example.org|normal| ?>
When a user wants to edit his profile, he must use edit account” option in the “index.php” page and enter his login information. However, using “|” as a parameter delimiter on email field followed by “admin”, the user could elevate his privileges to administrator. Example:
Username: Alice Password: 87654321 Email: email@example.com |admin|
This information will be recorded in “mem.php” file like this:
In this case, the last parameter delimiter considered is “|admin|” and the user could elevate his privileges by assigning administrator profile.
Although this vulnerability doesn’t allow manipulation of others user profiles, it allows privilege escalation for application users.