Security Test: CRLF Injection¶

Description¶

Default Severity: medium

CRLF injection happens when an attacker tricks your system into inserting unintended carriage return and newline characters in HTTP headers. This allows them to end one header and start another, potentially giving them the power to craft rogue requests or inject malicious headers. The risk is significant because it can lead to altered responses, redirections, or even sensitive data leaks if the attackers control parts of the HTTP exchange. Developers often fall into pitfalls by not properly sanitizing inputs that may be inserted into headers, assuming that trusted data won’t include newline characters. It's a sharp reminder to always clean and validate any data used in constructing HTTP responses.

Reference:

• http://www.watchfire.com/resources/HTTPResponseSplitting.pdf

Configuration¶

Identifier: injection/crlf

Examples¶

All configuration available:

checks:
  injection/crlf:
    skip: false # default

Compliance and Standards¶