CWE-93: Improper Neutralization of CRLF Sequences ('CRLF Injection')
CWE版本: 4.18
更新日期: 2025-09-09
弱点描述
The product uses CRLF (carriage return line feeds) as a special element, e.g. to separate lines or records, but it does not neutralize or incorrectly neutralizes CRLF sequences from inputs.
常见后果
影响范围: Integrity
技术影响: Modify Application Data
潜在缓解措施
阶段: Implementation
描述: Avoid using CRLF as a special sequence.
阶段: Implementation
描述: Appropriately filter or quote CRLF sequences in user-controlled input.
检测方法
方法: Automated Static Analysis
Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
有效性: High
观察示例
参考: CVE-2002-1771
CRLF injection enables spam proxy (add mail headers) using email address or name.
参考: CVE-2002-1783
CRLF injection in API function arguments modify headers for outgoing requests.
参考: CVE-2004-1513
Spoofed entries in web server log file via carriage returns
参考: CVE-2006-4624
Chain: inject fake log entries with fake timestamps using CRLF injection
参考: CVE-2005-1951
Chain: Application accepts CRLF in an object ID, allowing HTTP response splitting.
参考: CVE-2004-1687
Chain: HTTP response splitting via CRLF in parameter related to URL.
引入模式
| 阶段 | 说明 |
|---|---|
| Implementation | REALIZATION: This weakness is caused during implementation of an architectural security tactic. |
适用平台
编程语言
分类映射
| 分类名称 | 条目ID | 条目名称 | 映射适配度 |
|---|---|---|---|
| PLOVER | - | CRLF Injection | - |
| OWASP Top Ten 2007 | A2 | Injection Flaws | CWE More Specific |
| WASC | 24 | HTTP Request Splitting | - |
| Software Fault Patterns | SFP24 | Tainted input to command | - |