XSS Through Parameter Pollution
In this blog, I was able to perform an XSS attack with the help of Parameter pollution which bypasses target’s restriction.
I am Saajan Bhujel.
Student of Bachelor of Commerce(B.Com) and also I am a Bug Bounty Hunter.
This is my 2nd blog, if you find any spelling mistakes, so please bear with me for the next few minutes. And, I found this vulnerability in the VDP Program. But before starting this blog I would like to give a piece of small basic information about Cross-site Scripting (XSS) and HTTP Parameter Pollution (HPP).
What is the Cross-site Scripting (XSS)?
Cross-site scripting (also known as XSS) is a web security vulnerability that allows an attacker to inject malicious code into a vulnerable web application.
There are three main types of XSS attacks. These are:
- Reflected XSS: where the malicious script comes from the current HTTP request.
- Stored XSS: where the malicious script comes from the website’s database.
- DOM-based XSS: where the vulnerability exists in client-side code rather than server-side code.
What is the HTTP Parameter Pollution (HPP)?
HTTP Parameter Pollution, as implied by the name, pollutes the HTTP parameters of a web application in order to perform or achieve a specific malicious task/attack different from the intended behavior of the web application. ***
Now let’s start the blog….
After spending some days in the programs of Hackerone and Bugcrowd. I got some vulnerabilities on those programs like CSRF and Business logic flaws. But, I got duplicates for all my reports. Then, I thought to myself that, this time hunt on some VDP Programs.
So, I started hunting to find some bugs in the VDP Programs. After 2–3 Hours of hunting, I found that one domain is using a callback parameter in the URL for redirecting users to another subdomain.
And also, I can’t disclose the name of the target. So, Let’s suppose that the target is site.com. And, the URL is something looks like this:
And, If I open the above link. Then, it will redirect me to
So after seeing this redirection, I tried to change the value of the callback parameter with the https://bing.com. Because I want to confirm that, the website is doing any kind of validation or not. If the website is doing validation or redirection only allows for subdomains of site.com then the website might be not vulnerable to Open Redirect. And, If the website is not doing any kind of validation then the website is vulnerable.
And, after changing the value of the callback parameter. Now, the URL is something looks like this:
And, If I open the above link. Then, it will also redirect me to bing.com. It means that the website is not doing any kind of validation and It’s vulnerable to Open Redirect. But, after seeing the response of it in the Burpsuite. I thought that, maybe this is also vulnerable for the Cross Site Scripting because the value of the callback parameter is also reflecting back into the response.
So firstly, I tried to break the code because the value is reflecting in the script tag. For, break the variable callbackUrl, I simply put
anything%22; in the callback parameter. But, after sending this request I got an error that blocks my request. And, also I am getting the same error for some other values
Now, I have only two options:
- The first option is to report this issue as an Open Redirect.
- The second option is to find a bypass for getting an XSS.
Then, I remember that some weeks ago, I watched the video of Pwnfunction on HTTP Parameter Pollution. So, I choose the second option is to find a bypass for getting an XSS. And also, I added one more callback parameter in the URL for doing a Parameter pollution attack. And now, the URL is something looks like this:
And, I noticed that if I add two same parameters in the URL. Then, I will get the values of both parameters in the response separated by a comma.
And, you also know that when I used the values
[like ‘,”] that time I got an error that blocks my request. But now, I have two same parameters.
So again, I tried to break the variable callbackUrl. But this time, I put
%22;something%2f%2f in the second callback parameter. After adding the value, now the URL is something looks like this:
And, it works I am able to break the code or bypass the filter. It means that website is not doing any validation for the second callback parameter.
Now this time, For getting an XSS alert, I put
%22;alert%281%29;%2f%2f in the second callback parameter. And now, the URL is something looks like this:
And again, The website blocks my request for using brackets. So, I replaced brackets with
URL encoded or ``. But still, I am getting error. Because the website is still doing some validation for all the parameters.
Then, again I used
`` with URL encoded(eg:
%60%60). And, Finally I succeed to bypass the filter. And, the final URL is something that looks like this:
So now, I am successfully able to bypass the filter and perform an XSS through Parameter Pollution. And, In my case, I am able to bypass some filters for some values
[like ‘,”] through parameter pollution attack.
TIP:- If you see that your target is doing some kind of validation checks on the parameters. Then, try to add one or more same parameters. For seeing any changes in the response of the website, maybe you can bypass the validation checks.
Thank you for reading this blog, and I hope you learn something.
Enjoy your day!….