HTTP Response Splitting Vulnerability
OWASP 2013-A1 OWASP 2017-A1 PCI v3.2- CAPEC-34 CWE-113 WSTG-INPV-15 WASC-25
HTTP response splitting is detected when:
- Data enters a web application via an untrusted source.
- The data is included in an HTTP response header sent to a web user without being validated for malicious characters.
This web server allows attacker to set arbitrary headers, take control of the body, or break the response into two or more separate responses.
The impact include:-
- Cross-User Defacement
- Cache Poisoning
- Cross-Site Scripting
- Page Hijacking
Mitigation / Precaution
This vulnerability can be avoided by:-
- Using URL-encoded strings before inclusion into HTTP headers. This include Location or Set-Cookie.
- Use modern Java EE application servers.