CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Response Splitting')
Versions of Ratpack 0.9.1 through and including 1.7.4 are vulnerable to HTTP Response Splitting,
if untrusted and unsanitized data is used to populate the headers of an HTTP response.
An attacker can utilize this vulnerability to have the server issue any HTTP response they specify.
If your application uses arbitrary user input as the value of a response header it is vulnerable.
If your application does not use arbitrary values as response header values, it is not vulnerable.
Previously, Ratpack did not validate response header values.
Now, adding a header value that contains the header value termination characters (CRLF) produces a runtime exception.
Since there is no mechanism for escaping or encoding the termination characters in a String, a runtime exception is necessary.
As potentially dangerous values now cause runtime exceptions, it is a good idea to continue to validate and sanitize any user-supplied values being used as response headers.
We would like to thank Jonathan Leitschuh for reporting this vulnerability.
Vulnerable Example
The following example server uses a query parameter value as a response header, without validating or sanitizing it.
RatpackServer startedServer = RatpackServer.start(server -> {
server.handlers(chain -> chain.all(ctx -> {
// User supplied query parameter
String header = ctx.getRequest().getQueryParams().get("header");
// User supplied data used to populate a header value.
ctx.header("the-header", header)
.render("OK!");
}));
});Sending a request to the server with the following value for the header query param would allow the execution of arbitrary Javascript.
Content-Type: text/html
X-XSS-Protection: 0
<script>alert(document.domain)</script>
Impact
- Cross-User Defacement
- Cache Poisoning
- Cross-Site Scripting
- Page Hijacking
Patches
This vulnerability has been patched in Ratpack version 1.7.5.
Root Cause
The root cause was due to using the netty DefaultHttpHeaders object with verification disabled.
https://github.com/ratpack/ratpack/blob/af1e8c8590f164d7dd84d4212886fad4ead99080/ratpack-core/src/main/java/ratpack/server/internal/NettyHandlerAdapter.java#L159
This vulnerability is now more clearly documented in the Netty documentation: netty/netty#9646
Workarounds
The workaround for this vulnerability is to either not use arbitrary input as response header values or validate such values before being used to ensure they don't contain a carriage return and/or line feed characters.
References
For more information
If you have any questions or comments about this advisory:
References
CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Response Splitting')
Versions of Ratpack 0.9.1 through and including 1.7.4 are vulnerable to HTTP Response Splitting,
if untrusted and unsanitized data is used to populate the headers of an HTTP response.
An attacker can utilize this vulnerability to have the server issue any HTTP response they specify.
If your application uses arbitrary user input as the value of a response header it is vulnerable.
If your application does not use arbitrary values as response header values, it is not vulnerable.
Previously, Ratpack did not validate response header values.
Now, adding a header value that contains the header value termination characters (CRLF) produces a runtime exception.
Since there is no mechanism for escaping or encoding the termination characters in a String, a runtime exception is necessary.
As potentially dangerous values now cause runtime exceptions, it is a good idea to continue to validate and sanitize any user-supplied values being used as response headers.
We would like to thank Jonathan Leitschuh for reporting this vulnerability.
Vulnerable Example
The following example server uses a query parameter value as a response header, without validating or sanitizing it.
Sending a request to the server with the following value for the
headerquery param would allow the execution of arbitrary Javascript.Impact
Patches
This vulnerability has been patched in Ratpack version 1.7.5.
Root Cause
The root cause was due to using the netty
DefaultHttpHeadersobject with verification disabled.https://github.com/ratpack/ratpack/blob/af1e8c8590f164d7dd84d4212886fad4ead99080/ratpack-core/src/main/java/ratpack/server/internal/NettyHandlerAdapter.java#L159
This vulnerability is now more clearly documented in the Netty documentation: netty/netty#9646
Workarounds
The workaround for this vulnerability is to either not use arbitrary input as response header values or validate such values before being used to ensure they don't contain a carriage return and/or line feed characters.
References
For more information
If you have any questions or comments about this advisory:
References