Skip to content
OpenAdvisories

Weakness (CWE)

CWE-444: Inconsistent Interpretation of HTTP Requests

Base Incomplete

The 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.

More detail

HTTP requests or responses ("messages") can be
malformed or unexpected in ways that cause web servers or
clients to interpret the messages in different ways than
intermediary HTTP agents such as load balancers, reverse
proxies, web caching proxies, application firewalls,
etc. For example, an adversary may be able to add duplicate
or different header fields that a client or server might
interpret as one set of messages, whereas the intermediary
might interpret the same sequence of bytes as a different
set of messages. For example, discrepancies can arise in
how to handle duplicate headers like two Transfer-encoding
(TE) or two Content-length (CL), or the malicious HTTP
message will have different headers for TE and
CL.

The inconsistent parsing and interpretation of messages
can allow the adversary to "smuggle" a message to the
client/server without the intermediary being aware of it.

This weakness is usually the result of the usage
of outdated or incompatible HTTP protocol versions in the
HTTP agents.

How to prevent it (4 mitigations)
  1. Implementation

    Use a web server that employs a strict HTTP parsing procedure, such as Apache [REF-433].

  2. Implementation

    Use only SSL communication.

  3. Implementation

    Terminate the client session after each request.

  4. System Configuration

    Turn all pages to non-cacheable.

Source: MITRE CWE-444

73 results · Clear filters · Feed

  • Critical 9.1

    In Menlo On-Premise Appliance before 2.88, web policy may not be consistently applied properly to intentionally malform…

  • Critical 9.1

    Waitress has request processing race condition in HTTP pipelining with invalid first request

    Waitress is a Web Server Gateway Interface server for Python 2 and 3. A remote client may send a request that is exactly recv_bytes (defaults to 8192) long, followed by a secondary request using HTTP pipelining. When request lookahead is disabled (default) we…

  • Critical 9.1

    [20240802] - Core - Cache Poisoning in Pagination

    The pagination class includes arbitrary parameters in links, leading to cache poisoning attack vectors.

  • Critical 9.1

    Apache Traffic Server: Incomplete check for chunked trailer section allows request smuggling

    Apache Traffic Server forwards malformed HTTP chunked trailer section to origin servers. This can be utilized for request smuggling and may also lead cache poisoning if the origin servers are vulnerable. This issue affects Apache Traffic Server: from 8.0.0 th…

  • Critical 10.0
    CVE-2024-41110 Public exploit EPSS 16%

    Moby authz zero length regression

    Moby is an open-source project created by Docker for software containerization. A security vulnerability has been detected in certain versions of Docker Engine, which could allow an attacker to bypass authorization plugins (AuthZ) under specific circumstances…

  • Critical 9.8

    An issue was discovered in Elspec G5 digital fault recorder versions 1.1.4.15 and before. Unauthenticated memory corrup…

  • Critical 9.8

    HTTP Handling Vulnerability in the Bare server

    TOMP Bare Server implements the TompHTTP bare server. A vulnerability in versions prior to 2.0.2 relates to insecure handling of HTTP requests by the @tomphttp/bare-server-node package. This flaw potentially exposes the users of the package to manipulation of…

  • Critical 9.6
    CVE-2023-48365 Exploited · Ransomware EPSS 48%

    Qlik Sense Enterprise for Windows before August 2023 Patch 2 allows unauthenticated remote code execution, aka QB-21683…

    KEV Jan 13, 2025
  • Critical 9.3

    Squid: request/response smuggling in http/1.1 and icap

    SQUID is vulnerable to HTTP request smuggling, caused by chunked decoder lenience, allows a remote attacker to perform Request/Response smuggling past firewall and frontend security systems.

  • Critical 9.6
    CVE-2023-41265 Exploited · Ransomware Public exploit Scanner template EPSS 88%

    An HTTP Request Tunneling vulnerability found in Qlik Sense Enterprise for Windows for versions May 2023 Patch 3 and ea…

    KEV Dec 7, 2023
  • Critical 9.1

    Apache Traffic Server: Differential fuzzing for HTTP request parsing discrepancies

    Improper Input Validation vulnerability in Apache Software Foundation Apache Traffic Server.This issue affects Apache Traffic Server: through 9.2.1.

  • Critical 9.1
    CVE-2023-33193 Scanner template

    Emby Server Proxy Header Spoofing Vulnerability

    Emby Server is a user-installable home media server which stores and organizes a user's media files of virtually any format and makes them available for viewing at home and abroad on a broad range of client devices. This vulnerability may allow administrative…

  • Critical 9.8

    SwiftNIO vulnerable to HTTP request smuggling using malformed Transfer-Encoding header

    ### Impact Affected SwiftNIO systems are vulnerable to request smuggling attacks, in which they parse a given HTTP message differently from other network parties, potentially seeing a different number of requests than other servers. This can lead to failures …

  • Critical 9.8

    LavaLite vulnerable to web cache poisoning

    LavaLite CMS v 9.0.0 was discovered to be vulnerable to web cache poisoning.

  • Critical 9.8

    X-Forwarded-For header allows brute-forcing autoblocked IP addresses

    An issue was discovered in MediaWiki before 1.35.10, 1.36.x through 1.38.x before 1.38.6, and 1.39.x before 1.39.3. An auto-block can occur for an untrusted X-Forwarded-For header.

  • Critical 9.8
    CVE-2023-25690 Public exploit EPSS 84%

    Apache HTTP Server: HTTP request splitting with mod_rewrite and mod_proxy

    Some mod_proxy configurations on Apache HTTP Server versions 2.4.0 through 2.4.55 allow a HTTP Request Smuggling attack. Configurations are affected when mod_proxy is enabled along with some form of RewriteRule or ProxyPassMatch in which a non-specific patter…

  • Critical 9.1
    CVE-2023-25725 Public exploit

    HAProxy before 2.7.3 may allow a bypass of access control because HTTP/1 headers are inadvertently lost in some situati…

  • Critical 9.0

    Apache HTTP Server: mod_proxy_ajp Possible request smuggling

    Inconsistent Interpretation of HTTP Requests ('HTTP Request Smuggling') vulnerability in mod_proxy_ajp of Apache HTTP Server allows an attacker to smuggle requests to the AJP server it forwards requests to. This issue affects Apache HTTP Server Apache HTTP Se…

  • Critical 9.8
    CVE-2022-2466 Public exploit

    Quarkus does not terminate HTTP requests header context

    It was found that Quarkus 2.10.x does not terminate HTTP requests header context which may lead to unpredictable behavior.

  • Critical 9.1
    CVE-2022-32214 EPSS 82%

    llhttp allows HTTP Request Smuggling via Improper Delimiting of Header Fields

    The llhttp parser <v14.20.1, <v16.17.1 and <v18.9.1 in the http module in Node.js does not strictly use the CRLF sequence to delimit HTTP requests. This can lead to HTTP Request Smuggling (HRS).

  • Critical 9.1
    CVE-2022-32213 EPSS 45%

    llhttp allows HTTP Request Smuggling via Flawed Parsing of Transfer-Encoding

    The llhttp parser <v14.20.1, <v16.17.1 and <v18.9.1 in the http module in Node.js does not correctly parse and validate Transfer-Encoding headers and can lead to HTTP Request Smuggling (HRS).

  • Critical 9.1

    HTTP Request Smuggling in puma

    Puma is a simple, fast, multi-threaded, parallel HTTP 1.1 server for Ruby/Rack applications. When using Puma behind a proxy that does not properly validate that the incoming HTTP request matches the RFC7230 standard, Puma and the frontend proxy may disagree o…

  • Critical 9.8

    Insufficient Protection against HTTP Request Smuggling in mitmproxy

    mitmproxy is an interactive, SSL/TLS-capable intercepting proxy. In mitmproxy 7.0.4 and below, a malicious client or server is able to perform HTTP request smuggling attacks through mitmproxy. This means that a malicious client/server could smuggle a request/…

  • Critical 9.8
    CVE-2022-22536 Exploited Public exploit Scanner template EPSS 98%

    SAP NetWeaver Application Server ABAP, SAP NetWeaver Application Server Java, ABAP Platform, SAP Content Server 7.53 an…

    KEV Aug 18, 2022
  • Critical —

    Webcache Poisoning in shopware/platform and shopware/core

    ### Impact Webcache Poisoning via X-Forwarded-Prefix and sub-request ### Patches We recommend updating to the current version 6.4.6.1. You can get the update to 6.4.6.1 regularly via the Auto-Updater or directly via the download overview. https://www.shopware…

  • Critical 9.8
    CVE-2021-30180 Public exploit EPSS 60%

    Apache Dubbo RCE on customers via Condition route poisoning (Unsafe YAML unmarshaling)

    Apache Dubbo prior to 2.7.9 support Tag routing which will enable a customer to route the request to the right server. These rules are used by the customers when making a request in order to find the right endpoint. When parsing these YAML rules, Dubbo custom…

  • Critical 9.8

    HTTP Request Smuggling in hyper

    An issue was discovered in the hyper crate before 0.12.34 for Rust. HTTP request smuggling can occur. Remote code execution can occur in certain situations with an HTTP server on the loopback interface.

  • Critical 9.8

    Micronaut's HTTP client is vulnerable to HTTP Request Header Injection

    All versions of io.micronaut:micronaut-http-client before 1.2.11 and all versions from 1.3.0 before 1.3.2 are vulnerable to HTTP Request Header Injection due to not validating request headers passed to the client.

  • Critical 9.8

    Improper Input Validation in Twisted

    In Twisted Web through 19.10.0, there was an HTTP request splitting vulnerability. When presented with two content-length headers, it ignored the first header. When the second content-length value was set to zero, the request body was interpreted as a pipelin…

  • Critical 9.8

    HTTP Request Smuggling in Twisted

    In Twisted Web through 19.10.0, there was an HTTP request splitting vulnerability. When presented with a content-length and a chunked encoding header, the content-length took precedence and the remainder of the request body was interpreted as a pipelined requ…

  • Critical 9.1

    HTTP Request Smuggling in Netty

    HttpObjectDecoder.java in Netty before 4.1.44 allows an HTTP header that lacks a colon, which might be interpreted as a separate header with an incorrect syntax, or might be interpreted as an "invalid fold."

  • Critical 9.8
    CVE-2017-7658 EPSS 19%

    Jetty vulnerable to authorization bypass due to inconsistent HTTP request handling (HTTP Request Smuggling)

    In Eclipse Jetty Server, versions 9.2.x and older, 9.3.x (all non HTTP/1.x configurations), and 9.4.x (all HTTP/1.x configurations), when presented with two content-lengths headers, Jetty ignored the second. When presented with a content-length and a chunked …

  • Critical 9.8
    CVE-2017-7657 EPSS 14%

    Critical severity vulnerability that affects org.eclipse.jetty:jetty-server

    In Eclipse Jetty, versions 9.2.x and older, 9.3.x (all configurations), and 9.4.x (non-default configuration with RFC2616 compliance enabled), transfer-encoding chunks are handled poorly. The chunk length parsing was vulnerable to an integer overflow. Thus a …