CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting')
low-riskThe product receives data from an HTTP agent/component (e.g., web server, proxy, browser, etc.), but it does not neutralize or incorrectly neutralizes CR and LF characters before the data is included in outgoing HTTP headers.
Abstraction: Variant
Common Consequences
Integrity
→
Modify Application Data
Detection Methods
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.)
Real-World Examples (10)
| CVE | CVSS | EPSS | KEV |
|---|---|---|---|
| CVE-2024-52875 | 8.8 | 78.6% | — |
| CVE-2016-5699 | 6.1 | 35.3% | — |
| CVE-2018-16979 | 6.1 | 18.0% | — |
| CVE-2024-40324 | 5.4 | 12.0% | — |
| CVE-2016-8024 | 8.1 | 9.2% | — |
| CVE-2023-0508 | 3.1 | 4.0% | — |
| CVE-2018-7830 | 7.5 | 2.7% | — |
| CVE-2020-5247 | 6.5 | 2.1% | — |
| CVE-2024-42487 | 4.0 | 1.8% | — |
| CVE-2016-4993 | 6.1 | 1.5% | — |
4
/ 100
low-risk
Active Threat
4/50 · Minimal
Exploit Availability
0/50 · Minimal