CWE-444: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')
low-riskThe product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination.
Common Consequences
Detection Methods
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-2022-22536 | 10.0 | 93.8% | Y |
| CVE-2022-22536 | 10.0 | 93.8% | Y |
| CVE-2023-41265 | 9.6 | 92.5% | Y |
| CVE-2023-41265 | 9.6 | 92.5% | Y |
| CVE-2022-32213 | 6.5 | 89.6% | — |
| CVE-2022-32213 | 6.5 | 89.6% | — |
| CVE-2022-32215 | 6.5 | 88.8% | — |
| CVE-2022-32215 | 6.5 | 88.8% | — |
| CVE-2020-9490 | 7.5 | 76.3% | — |
| CVE-2019-20372 | 5.3 | 69.7% | — |