Difference between revisions of "Parameter Delimiter"
(Reverting to last version not containing links to s1.shard.jp)
|(7 intermediate revisions by 2 users not shown)|
Latest revision as of 07:50, 3 June 2009
Last revision (mm/dd/yy): 06/3/2009
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, we will use 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 the 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 the "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 other users' profiles, it allows privilege escalation for application users.