How to fix: HTTP Request Smuggling Indicator
Both Transfer-Encoding: chunked and Content-Length headers are present in the same response, which is a condition that can enable HTTP request smuggling attacks when a front-end proxy and backend server disagree on which header to use.
Why it matters
HTTP request smuggling allows attackers to bypass security controls, poison shared caches, access other users' requests, and in some configurations achieve SSRF or remote code execution. It exploits disagreement between load balancers and backend servers about message boundaries.
HTTP/1.1 specifies that when both Transfer-Encoding and Content-Length are present, Transfer-Encoding takes precedence. When front-end (proxy) and back-end servers interpret these headers differently, an attacker can 'smuggle' a prefix of a request that the back-end processes as the next request.
How to fix it
- 1Ensure your proxy and backend use the same HTTP message framing.
- 2Configure your reverse proxy to rewrite or normalize ambiguous transfer encoding.
- 3Upgrade to HTTP/2 end-to-end: HTTP/2 is not vulnerable to classical request smuggling.
- 4Use Burp Suite's HTTP Request Smuggler extension to actively test your setup.
Code examples
Nginx fix: normalize Transfer-Encoding
# Reject requests with both TE and CL (defense)
http {
# Keep backend on HTTP/1.1 and normalize chunked encoding
proxy_http_version 1.1;
proxy_set_header Connection '';
# Upgrade proxy-to-backend to HTTP/2 when possible
}References
Detected automatically by VulnRadar. The check id is http-request-smuggling, stable across every scan so you can filter or diff on it.
More host validation checks
- HighHost Header Injection Risk
- MediumSymfony Debug Token Header Exposed
- HighHTTP Basic Authentication Over Non-HTTPS
- MediumASP.NET ViewState Without MAC Protection
- HighCache Poisoning via Unkeyed Headers
- LowSequential Numeric ID in URL (IDOR Risk)
- HighConfirmed Open Redirect via Location Header
- HighConfirmed Open Redirect via Meta Refresh
Questions
- How severe is HTTP Request Smuggling Indicator?
- VulnRadar rates this high severity in the host validation category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id http-request-smuggling, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does HTTP Request Smuggling Indicator map to?
- It maps to CWE-444. In the OWASP Top 10 it falls under A05:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.