cwe-113-http-response-splitting

To remediate CWE-113 HTTP Response Splitting in Java code, sanitize user-controlled input used in HTTP headers and cookies by applying strict input validation and output encoding to prevent CRLF injection.

HTTP Response Splitting is a vulnerability where attackers inject malicious content into HTTP headers via CRLF injection. It affects web applications by allowing the attacker to manipulate the response body or headers.

Sanitize user input in Java HTTP response headers and cookies by validating the data against strict whitelists and encoding output. This prevents unauthorized carriage return and line feed characters from being interpreted.

Yes, you can automatically fix a SAST flagged response.addHeader vulnerability by applying deterministic code transformations that replace unvalidated user input with secure, sanitized header manipulation methods.

You need to validate input for HTTP Response Splitting vulnerabilities whenever your Java web application performs direct manipulation of HTTP response headers or cookies using data originating from user-controlled sources.

The best way to prevent CRLF injection in Java web frameworks is to implement robust header sanitization methods that strip or encode CR and LF characters from user-supplied strings before adding them to HTTP responses.