Search vulnerabilities

Results 518

Export CSV
CVE-2020-11993

httpd: mod_http2 concurrent pool usage

Apache HTTP Server versions 2.4.20 to 2.4.43 When trace/debug was enabled for the HTTP/2 module and on certain traffic edge patterns, logging statements were made on the wrong connection, causing concurrent use of memory pools. Configuring the LogLevel of mod_http2 above "info" will mitigate this vulnerability for unpatched servers.

CVSS 3.1 · 7.5 High EPSS 56.6% KEV · Not listed
Vendors
Apache Canonical Debian and 5 more
Products
CVE-2022-26377

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 Server 2.4 version 2.4.53 and prior versions.

CVSS 3.1 · 7.5 High EPSS 21.1% KEV · Not listed
Vendors
CVE-2023-27522

Apache HTTP Server: mod_proxy_uwsgi HTTP response splitting

HTTP Response Smuggling vulnerability in Apache HTTP Server via mod_proxy_uwsgi. This issue affects Apache HTTP Server: from 2.4.30 through 2.4.55. Special characters in the origin response header can truncate/split the response forwarded to the client.

CVSS 3.1 · 7.5 High EPSS 2.1% KEV · Not listed
Vendors
Apache Debian Redhat and 1 more
CVE-2022-45059

varnish: Request Smuggling Vulnerability

An issue was discovered in Varnish Cache 7.x before 7.1.2 and 7.2.x before 7.2.1. A request smuggling attack can be performed on Varnish Cache servers by requesting that certain headers are made hop-by-hop, preventing the Varnish Cache servers from forwarding critical headers to the backend.

CVSS 3.1 · 7.5 High EPSS 1.8% KEV · Not listed
CVE-2022-35256

nodejs: HTTP Request Smuggling due to incorrect parsing of header fields

The llhttp parser in the http module in Node v18.7.0 does not correctly handle header fields that are not terminated with CLRF. This may result in HTTP Request Smuggling.

CVSS 3.1 · 6.5 Medium EPSS 2.8% KEV · Not listed
Vendors
Debian Llhttp Nodejs and 2 more
Products
CVE-2022-32213

nodejs: HTTP request smuggling due to 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).

CVSS 3.1 · 6.5 Medium EPSS 44.8% KEV · Not listed
Vendors
Products
CVE-2022-32214

nodejs: HTTP request smuggling due to 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).

CVSS 3.1 · 6.5 Medium EPSS 81.8% KEV · Not listed
Vendors
Debian Llhttp Nodejs and 2 more
Products
CVE-2022-32215

nodejs: HTTP request smuggling due to incorrect parsing of multi-line 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 handle multi-line Transfer-Encoding headers. This can lead to HTTP Request Smuggling (HRS).

CVSS 3.1 · 6.5 Medium EPSS 70.2% KEV · Not listed
Vendors
Products
CVE-2021-22960

llhttp: HTTP Request Smuggling when parsing the body of chunked requests

The parse function in llhttp < 2.1.4 and < 6.0.6. ignores chunk extensions when parsing the body of chunked requests. This leads to HTTP Request Smuggling (HRS) under certain conditions.

CVSS 3.1 · 6.5 Medium EPSS 2.5% KEV · Not listed
Vendors
Debian Llhttp Oracle and 1 more
Products
CVE-2021-22959

llhttp: HTTP Request Smuggling due to spaces in headers

The parser in accepts requests with a space (SP) right after the header name before the colon. This can lead to HTTP Request Smuggling (HRS) in llhttp < v2.1.4 and < v6.0.6.

CVSS 3.1 · 6.5 Medium EPSS 3.2% KEV · Not listed
Vendors
Debian Llhttp Oracle and 1 more
Products
CVE-2020-8287

nodejs: HTTP request smuggling via two copies of a header field in an http request

Node.js versions before 10.23.1, 12.20.1, 14.15.4, 15.5.1 allow two copies of a header field in an HTTP request (for example, two Transfer-Encoding header fields). In this case, Node.js identifies the first header field and ignores the second. This can lead to HTTP Request Smuggling.

CVSS 3.1 · 6.5 Medium EPSS 16.3% KEV · Not listed
Vendors
Products
CVE-2020-8201

nodejs: HTTP request smuggling due to CR-to-Hyphen conversion

Node.js < 12.18.4 and < 14.11 can be exploited to perform HTTP desync attacks and deliver malicious payloads to unsuspecting users. The payloads can be crafted by an attacker to hijack user sessions, poison cookies, perform clickjacking, and a multitude of other attacks depending on the architecture of the underlying system. The attack was possible due to a bug in processing of carrier-return symbols in the HTTP header names.

CVSS 3.1 · 7.4 High EPSS 5.3% KEV · Not listed
Vendors
Products
Fedora Node.js Leap and 3 more
CVE-2019-15605

nodejs: HTTP request smuggling using malformed Transfer-Encoding header

HTTP request smuggling in Node.js 10, 12, and 13 causes malicious payload delivery when transfer-encoding is malformed

CVSS 3.1 · 9.8 Critical EPSS 57.1% KEV · Not listed
Vendors
Products
CVE-2024-53868

Apache Traffic Server: Malformed chunked message body allows request smuggling

Apache Traffic Server allows request smuggling if chunked messages are malformed.  This issue affects Apache Traffic Server: from 9.2.0 through 9.2.9, from 10.0.0 through 10.0.4. Users are recommended to upgrade to version 9.2.10 or 10.0.5, which fixes the issue.

CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Vendors
Products
CVE-2024-35538

Typecho v1.3.0 was discovered to contain a Client IP Spoofing vulnerability, which allows attackers to falsify their IP addresses by specifying an arbitrary IP as value of X-Forwarded-For or Client-Ip headers while performing HTTP requests.

CVSS 3.1 · 5.3 Medium EPSS < 1% KEV · Not listed
Vendors
Products
CVE-2022-38114

Client-Side Desync Vulnerability

This vulnerability occurs when a web server fails to correctly process the Content-Length of POST requests. This can lead to HTTP request smuggling or XSS.

CVSS 3.1 · 6.1 Medium EPSS < 1% KEV · Not listed
Vendors
CVE-2022-24761

HTTP Request Smuggling in waitress

Waitress is a Web Server Gateway Interface server for Python 2 and 3. When using Waitress versions 2.1.0 and prior behind a proxy that does not properly validate the incoming HTTP request matches the RFC7230 standard, Waitress and the frontend proxy may disagree on where one request starts and where it ends. This would allow requests to be smuggled via the front-end proxy to waitress and later behavior. There are two classes of vulnerability that may lead to request smuggling that are addressed by this advisory: The use of Python's `int()` to parse strings into integers, leading to `+10` to be parsed as `10`, or `0x01` to be parsed as `1`, where as the standard specifies that the string should contain only digits or hex digits; and Waitress does not support chunk extensions, however it was discarding them without validating that they did not contain illegal characters. This vulnerability has been patched in Waitress 2.1.1. A workaround is available. When deploying a proxy in front of waitress, turning on any and all functionality to make sure that the request matches the RFC7230 standard. Certain proxy servers may not have this functionality though and users are encouraged to upgrade to the latest version of waitress instead.

CVSS 3.1 · 7.5 High EPSS 1.8% KEV · Not listed
CVE-2022-24766

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/response through mitmproxy as part of another request/response's HTTP message body. While mitmproxy would only see one request, the target server would see multiple requests. A smuggled request is still captured as part of another request's body, but it does not appear in the request list and does not go through the usual mitmproxy event hooks, where users may have implemented custom access control checks or input sanitization. Unless mitmproxy is used to protect an HTTP/1 service, no action is required. The vulnerability has been fixed in mitmproxy 8.0.0 and above. There are currently no known workarounds.

CVSS 3.1 · 9.8 Critical EPSS 1.6% KEV · Not listed
Vendors
Products
CVE-2022-24790

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 on where a request starts and ends. This would allow requests to be smuggled via the front-end proxy to Puma. The vulnerability has been fixed in 5.6.4 and 4.3.12. Users are advised to upgrade as soon as possible. Workaround: when deploying a proxy in front of Puma, turning on any and all functionality to make sure that the request matches the RFC7230 standard.

CVSS 3.1 · 9.1 Critical EPSS 2.2% KEV · Not listed
Vendors
Products
Debian Linux Fedora Puma and 2 more
CVE-2022-24801

HTTP Request Smuggling in twisted.web

Twisted is an event-based framework for internet applications, supporting Python 3.6+. Prior to version 22.4.0rc1, the Twisted Web HTTP 1.1 server, located in the `twisted.web.http` module, parsed several HTTP request constructs more leniently than permitted by RFC 7230. This non-conformant parsing can lead to desync if requests pass through multiple HTTP parsers, potentially resulting in HTTP request smuggling. Users who may be affected use Twisted Web's HTTP 1.1 server and/or proxy and also pass requests through a different HTTP server and/or proxy. The Twisted Web client is not affected. The HTTP 2.0 server uses a different parser, so it is not affected. The issue has been addressed in Twisted 22.4.0rc1. Two workarounds are available: Ensure any vulnerabilities in upstream proxies have been addressed, such as by upgrading them; or filter malformed requests by other means, such as configuration of an upstream proxy.

CVSS 3.1 · 8.1 High EPSS 2.8% KEV · Not listed
Vendors