CWE-444Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')

Description

Common consequences· 1

• Integrity / Non-Repudiation / Access Control — Unexpected State, Hide Activities, Bypass Protection Mechanism
  An attacker could create HTTP messages to exploit a number of weaknesses including 1) the message can trick the web server to associate a URL with another URL's webpage and caching the contents of the webpage (web cache poisoning attack), 2) the message can be structured to bypass the firewall protection mechanisms and gain unauthorized access to a web application, and 3) the message can invoke a script or a page that returns client credentials (similar to a Cross Site Scripting attack).

Potential mitigations· 4

• [Implementation]Use a web server that employs a strict HTTP parsing procedure, such as Apache [REF-433].
• [Implementation]Use only SSL communication.
• [Implementation]Terminate the client session after each request.
• [System Configuration]Turn all pages to non-cacheable.

Related CAPEC attack patterns· 2

Exploits (incoming)2

(incoming)26

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.