CVE Vulnerabilities

CVE-2023-46589

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

Published: Nov 28, 2023 | Modified: Nov 21, 2024
CVSS 3.x
7.5
HIGH
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
CVSS 2.x
RedHat/V2
RedHat/V3
7.5 IMPORTANT
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Ubuntu
MEDIUM

Improper Input Validation vulnerability in Apache Tomcat.Tomcat from 11.0.0-M1 through 11.0.0-M10, from 10.1.0-M1 through 10.1.15, from 9.0.0-M1 through 9.0.82 and from 8.5.0 through 8.5.95 did not correctly parse HTTP trailer headers. A trailer header that exceeded the header size limit could cause Tomcat to treat a single request as multiple requests leading to the possibility of request smuggling when behind a reverse proxy.

Users are recommended to upgrade to version 11.0.0-M11 onwards, 10.1.16 onwards, 9.0.83 onwards or 8.5.96 onwards, which fix the issue.

Weakness

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.

Affected Software

Name Vendor Start Version End Version
Tomcat Apache 8.5.0 (including) 8.5.96 (excluding)
Tomcat Apache 9.0.0 (including) 9.0.83 (excluding)
Tomcat Apache 10.1.0 (including) 10.1.16 (excluding)
Tomcat Apache 11.0.0-milestone1 (including) 11.0.0-milestone1 (including)
Tomcat Apache 11.0.0-milestone10 (including) 11.0.0-milestone10 (including)
Tomcat Apache 11.0.0-milestone2 (including) 11.0.0-milestone2 (including)
Tomcat Apache 11.0.0-milestone3 (including) 11.0.0-milestone3 (including)
Tomcat Apache 11.0.0-milestone4 (including) 11.0.0-milestone4 (including)
Tomcat Apache 11.0.0-milestone5 (including) 11.0.0-milestone5 (including)
Tomcat Apache 11.0.0-milestone6 (including) 11.0.0-milestone6 (including)
Tomcat Apache 11.0.0-milestone7 (including) 11.0.0-milestone7 (including)
Tomcat Apache 11.0.0-milestone8 (including) 11.0.0-milestone8 (including)
Tomcat Apache 11.0.0-milestone9 (including) 11.0.0-milestone9 (including)
JWS 5.7.8 RedHat tomcat *
JWS 6.0.1 RedHat tomcat *
Red Hat Enterprise Linux 8 RedHat tomcat-1:9.0.62-27.el8_9.3 *
Red Hat Enterprise Linux 8.8 Extended Update Support RedHat tomcat-1:9.0.62-5.el8_8.3 *
Red Hat Enterprise Linux 9 RedHat tomcat-1:9.0.62-37.el9_3.2 *
Red Hat Enterprise Linux 9.2 Extended Update Support RedHat tomcat-1:9.0.62-11.el9_2.4 *
Red Hat Fuse 7.13.0 RedHat tomcat *
Red Hat JBoss Web Server 5.7 on RHEL 7 RedHat jws5-tomcat-0:9.0.62-41.redhat_00020.1.el7jws *
Red Hat JBoss Web Server 5.7 on RHEL 8 RedHat jws5-tomcat-0:9.0.62-41.redhat_00020.1.el8jws *
Red Hat JBoss Web Server 5.7 on RHEL 9 RedHat jws5-tomcat-0:9.0.62-41.redhat_00020.1.el9jws *
Red Hat JBoss Web Server 6.0 on RHEL 8 RedHat jws6-tomcat-0:10.1.8-6.redhat_00013.1.el8jws *
Red Hat JBoss Web Server 6.0 on RHEL 9 RedHat jws6-tomcat-0:10.1.8-6.redhat_00013.1.el9jws *
Tomcat10 Ubuntu bionic *
Tomcat10 Ubuntu lunar *
Tomcat10 Ubuntu mantic *
Tomcat10 Ubuntu trusty *
Tomcat10 Ubuntu upstream *
Tomcat10 Ubuntu xenial *
Tomcat8 Ubuntu bionic *
Tomcat8 Ubuntu esm-apps/bionic *
Tomcat8 Ubuntu trusty *
Tomcat8 Ubuntu xenial *
Tomcat9 Ubuntu bionic *
Tomcat9 Ubuntu devel *
Tomcat9 Ubuntu esm-apps/bionic *
Tomcat9 Ubuntu esm-apps/jammy *
Tomcat9 Ubuntu focal *
Tomcat9 Ubuntu jammy *
Tomcat9 Ubuntu lunar *
Tomcat9 Ubuntu mantic *
Tomcat9 Ubuntu noble *
Tomcat9 Ubuntu oracular *
Tomcat9 Ubuntu trusty *
Tomcat9 Ubuntu upstream *
Tomcat9 Ubuntu xenial *

Extended Description

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.

Potential Mitigations

References