crlf-injection

To test for CRLF injection, you inject carriage return and line feed characters into HTTP headers, Location redirects, or Set-Cookie values to see if they manipulate the response. This skill detects those vulnerabilities and identifies common attack vectors automatically.

Yes, CRLF injection can escalate to XSS via double CRLF body injection and enable cache poisoning by injecting malicious headers. This skill demonstrates real-world exploitation chains including session fixation and XSS escalation scenarios.

Location redirects and Set-Cookie values are common targets for CRLF injection attacks. This skill identifies instances where CRLF can be injected into these headers, log files, and other HTTP response headers to manipulate web application behavior.

Encoding bypass techniques for CRLF injection involve using alternative character encodings to evade input validation filters. This skill demonstrates various encoding bypass methods and exploitation scenarios for web applications with filtering mechanisms.

Yes, detecting CRLF injection requires knowledge of HTTP response headers and common attack vectors. This skill focuses on HTTP header manipulation and response body injection, making header knowledge essential for identifying and exploiting these vulnerabilities.