沈阳地铁四号线 4月起进入主体施工阶段

百度 为了做好外来务工人员的消防安全管理工作，德清大队通过专业培训以及志愿者宣传等途径，着力提升外来务工人员的消防安全素质。

HTTP response splitting is a form of web application vulnerability, resulting from the failure of the application or its environment to properly sanitize input values. It can be used to perform cross-site scripting attacks, cross-user defacement, web cache poisoning, and similar exploits.

The attack consists of making the server print a carriage return (CR, ASCII 0x0D) line feed (LF, ASCII 0x0A) sequence followed by content supplied by the attacker in the header section of its response, typically by including them in input fields sent to the application. Per the HTTP standard (RFC 2616), headers are separated by one CRLF and the response's headers are separated from its body by two. Therefore, the failure to remove CRs and LFs allows the attacker to set arbitrary headers, take control of the body, or break the response into two or more separate responses—hence the name.

Prevention

The generic solution is to URL-encode strings before inclusion into HTTP headers such as Location or Set-Cookie.

Typical examples of sanitization include casting to integers or aggressive regular expression replacement. Most modern server-side scripting languages and runtimes, like PHP since version 5.1.2 and Node.js since 4.6.0 (previous versions supported it, but the protection could've been bypassed, which was discovered in 2016) as well as Web frameworks, such as Django since version 1.8.4 support sanitization of HTTP responses against this type of vulnerability.

External links

• Divide and Conquer - HTTP Response Splitting, Web Cache Poisoning Attacks, and Related Topics. Amit Klein, 2004.
• HTTP Response Splitting, The Web Application Security Consortium
• Wapiti Open Source XSS, Header, SQL and LDAP injection scanner
• LWN article
• CWE-113: Failure to Sanitize CRLF Sequences in HTTP Headers ('HTTP Response Splitting')
• HTTP Response Splitting Attack - OWASP
• CRLF Injection - OWASP