CRLF Injection - Revision history

Augustd: /* Related Attacks */ Added Log Injection

2018-03-14T16:50:54Z

‎Related Attacks: Added Log Injection

2016-05-03T14:57:09Z

2016-05-03T14:55:51Z

2009-02-21T13:40:45Z

‎Examples

2009-02-21T13:39:11Z

‎Description

2009-02-21T00:32:05Z

2009-02-21T00:31:56Z

2009-02-20T10:02:55Z

2009-02-18T02:08:33Z

2008-10-30T10:25:18Z

@@ Line 24: / Line 24: @@
 * [[HTTP Response Splitting]]
-* [[Attack 2]]
+* [[Log Injection]]
@@ Line 49: / Line 49: @@
 [[Category:FIXME|add links
 In addition, one should classify vulnerability based on the following subcategories: Ex:<nowiki>[[Category:Error Handling Vulnerability]]</nowiki>
 Availability Vulnerability
 Authorization Vulnerability
 Authentication Vulnerability
 Concurrency Vulnerability
 Configuration Vulnerability
 Cryptographic Vulnerability
 Encoding Vulnerability
 Error Handling Vulnerability
 Input Validation Vulnerability
 Logging and Auditing Vulnerability
 Session Management Vulnerability]]
 __NOTOC__
 [[Category:OWASP ASDR Project]]
 [[Category:Vulnerability]]
 [[Category:Implementation]]

@@ Line 6: / Line 6: @@
 ==Description==
-The term CRLF refers to '''C'''arriage '''R'''eturn (ASCII 13, \r) '''L'''ine '''F'''eed (ASCII 10, \n). They're used to note the termination of a line, however, dealt with differently in today’s popular Operating Systems. For example: in Windows both a CR and LF are required to note the end of a line, whereas in Linux/UNIX a LF is only required.
+The term CRLF refers to '''C'''arriage '''R'''eturn (ASCII 13, \r) '''L'''ine '''F'''eed (ASCII 10, \n). They're used to note the termination of a line, however, dealt with differently in today’s popular Operating Systems. For example: in Windows both a CR and LF are required to note the end of a line, whereas in Linux/UNIX a LF is only required. In the HTTP protocol, the CR-LF sequence is always used to terminate a line.
 A CRLF Injection attack occurs when a user manages to submit a CRLF into an application. This is most commonly done by modifying an HTTP parameter or URL.

@@ Line 23: / Line 23: @@
 ==Related [[Attacks]]==
-* [[Attack 1]]
+* [[HTTP Response Splitting]]
 * [[Attack 2]]

@@ Line 15: / Line 15: @@
 ==Examples==
-Depending on how the application is developed this can be a minor problem or a fairly serious security flaw. Lets look at the latter because this is after all a security related post.
+Depending on how the application is developed, this can be a minor problem or a fairly serious security flaw. Let's look at the latter because this is after all a security related post.
-Let's assume a file is used at some point to read/write data to, such as a log of some sort. If an attacker managed to place a CRLF then can then inject some sort of read programmatic method to the file. This could result in the contents being written to screen on the next attempt to use this file.
+Let's assume a file is used at some point to read/write data to  a log of some sort. If an attacker managed to place a CRLF then can then inject some sort of read programmatic method to the file. This could result in the contents being written to screen on the next attempt to use this file.
 ==Related [[Attacks]]==

@@ Line 8: / Line 8: @@
 The term CRLF refers to '''C'''arriage '''R'''eturn (ASCII 13, \r) '''L'''ine '''F'''eed (ASCII 10, \n). They're used to note the termination of a line, however, dealt with differently in today’s popular Operating Systems. For example: in Windows both a CR and LF are required to note the end of a line, whereas in Linux/UNIX a LF is only required.
-A CRLF Injection attack occurs when a user managed to submit a CRLF into an application. This is most commonly done by modifying an HTTP parameter or URL.
+A CRLF Injection attack occurs when a user manages to submit a CRLF into an application. This is most commonly done by modifying an HTTP parameter or URL.
 ==Risk Factors==

@@ Line 1: / Line 1: @@
 {{Template:Vulnerability}}
-<br>
 Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''