HTTP request smuggling

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

HTTP request smuggling is a security exploit on the HTTP protocol that uses inconsistency between the interpretation of Content-length and/or Transfer-encoding headers between HTTP server implementations in an HTTP proxy server chain.[1][2] It was first documented in 2005, and was again repopularized by PortSwigger's research.[3]

Types[edit]

CL.TE[edit]

In this type of HTTP request smuggling, the front end processes the request using Content-Length header while backend processes the request using Transfer-Encoding header.[3]

TE.CL[edit]

In this type of HTTP request smuggling, the front end processes request using Transfer-Encoding header while backend processes the request using Content-Length header.[3]

Prevention[edit]

HTTP/2 should be used for backend connections and web server accepting same type of HTTP header should be used. [3]

References[edit]

  1. ^ "CWE - CWE-444: Inconsistent Interpretation of HTTP Requests ('HTTP Request Smuggling') (4.0)". cwe.mitre.org. Retrieved 2020-03-13.
  2. ^ "What is HTTP request smuggling? Tutorial & Examples | Web Security Academy". portswigger.net. Retrieved 2020-03-13.
  3. ^ a b c d "HTTP request smuggling".