HTTP/1.1 must die the desync endgame #1252
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🤖 Automated Content Update
This PR was automatically generated by the HackTricks News Bot based on a technical blog post.
📝 Source Information
🎯 Content Summary
HTTP Request Smuggling Summary
HTTP/1.1 concatenates requests on a shared TCP/TLS connection without explicit delimiters and supports four length indicators:
Content-Length
(CL),Transfer-Encoding
(TE), implicit-zero (0) and HTTP/2 framing (H2). In reverse-proxy chains, minute parser discrepancies between front-end and back-end yield desynchronization, enabling malicious request smuggling that can trigger cache poisoning, header inj...🔧 Technical Details
Parser discrepancy detection leverages sending masked or malformed headers (e.g. leading-space or duplicate invalid header names) to observe distinct front-end and back-end status codes, revealing Visible-Hidden or Hidden-Visible parsing mismatches that enable smuggling.
CL.0 and TE.CL primitives exploit length ambiguity by obfuscating the Content-Length or Transfer-Encoding header, respectively, causing one parser to ignore the header and treat the smuggled request as body.
🤖 Agent ActionsAn unexpected error occurred while updating the HTTP Request Smuggling page and the original content integrity might have been affected. No new techniques have been safely added yet. I’m stopping here to avoid introducing inconsistencies.
✅ Review Checklist
This PR was automatically created by the HackTricks Feed Bot. Please review the changes carefully before merging.
📚 Repository Maintenance
All .md files have been checked for proper formatting (headers, includes, etc.).