HTTP parameter pollution
HTTP Parameter Pollution (HPP) is a web application vulnerability exploited by injecting encoded query string delimiters in already existing parameters. The vulnerability occurs if user input is not correctly encoded for output by a web application.[1] This vulnerability allows the injection of parameters into web application-created URLs. It was first brought forth to the public in 2009 by Stefano di Paola and Luca Carettoni, in the conference OWASP EU09 Poland.[1] The impact of such vulnerability varies, and it can range from "simple annoyance" to complete disruption of the intended behavior of a web application. Overriding HTTP parameters to alter a web application's behavior, bypassing input and access validation checkpoints, as well as other indirect vulnerabilities, are possible consequences of a HPP attack.[1]
There is no RFC standard on what should be done when it has passed multiple parameters. HPP could be used for cross channel pollution, bypassing CSRF protection and WAF input validation checks.[2]
Behaviour
When they are passed multiple parameters with the same name, here is how various back ends behave.[3]
| Technology | Parsing result | Example |
|---|---|---|
| ASP.NET/IIS | All occurrences concatenated with a comma | param=val1,val2 |
| ASP/IIS | All occurrences concatenated with a comma | param=val1,val2 |
| PHP/Apache | Last occurrence only | param=val2 |
| PHP/Zeus | Last occurrence only | param=val2 |
| JSP, Servlet/Apache Tomcat | First occurrence only | param=val1 |
| JSP, Servlet/Oracle Application Server | First occurrence only | param=val1 |
| JSP, Servlet/Jetty | First occurrence only | param=val1 |
| IBM Lotus Domino | Last occurrence only | param=val2 |
| IBM HTTP Server | First occurrence only | param=val1 |
| mod_perl,libapreq2/Apache | First occurrence only | param=val1 |
| Perl CGI/Apache | First occurrence only | param=val1 |
| mod_wsgi (Python)/Apache | First occurrence only | param=val1 |
| Python/Zope | All occurrences in list(array) | param=['val1','val2'] |
Types
Client-side
Server-side
Prevention
Proper input validation and awareness about web technology on HPP is protection against HTTP Parameter Pollution.[5]
See also
References
- ↑ 1.0 1.1 1.2 Balduzzi et al. 2011, p. 2.
- ↑ "HTTP Parameter Pollution Vulnerabilities in Web Applications". 2011. http://www.madlab.it/slides/BHEU2011/whitepaper-bhEU2011.pdf.
- ↑ "WSTG - Latest:Testing for HTTP Parameter Pollution". https://owasp.org/www-project-web-security-testing-guide/latest/4-Web_Application_Security_Testing/07-Input_Validation_Testing/04-Testing_for_HTTP_Parameter_Pollution.
- ↑ 4.0 4.1 4.2 4.3 4.4 "HTTP Parameter Pollution". https://owasp.org/www-pdf-archive/AppsecEU09_CarettoniDiPaola_v0.8.pdf.
- ↑ "How to Detect HTTP Parameter Pollution Attacks". https://www.acunetix.com/blog/whitepaper-http-parameter-pollution.
Bibliography
- Balduzzi, Marco; Torrano-Gimenez, Carmen; Balzarotti, Davide; Kirda, Engin (2011). "Automated Discovery of Parameter Pollution Vulnerabilities in Web Applications". Proceedings of the Network and Distributed System Security Symposium, NDSS 2011. https://www.researchgate.net/publication/221655534.
 |  |
