CVE Vulnerabilities

CVE-2021-31922

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

Published: May 14, 2021 | Modified: Jul 12, 2022
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
5 MEDIUM
AV:N/AC:L/Au:N/C:N/I:P/A:N
RedHat/V2
RedHat/V3
Ubuntu

An HTTP Request Smuggling vulnerability in Pulse Secure Virtual Traffic Manager before 21.1 could allow an attacker to smuggle an HTTP request through an HTTP/2 Header. This vulnerability is resolved in 21.1, 20.3R1, 20.2R1, 20.1R2, 19.2R4, and 18.2R3.

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
Virtual_traffic_manager Pulsesecure * 18.1 (including)
Virtual_traffic_manager Pulsesecure 18.3 (including) 19.1 (including)
Virtual_traffic_manager Pulsesecure 18.2 (including) 18.2 (including)
Virtual_traffic_manager Pulsesecure 18.2-r1 (including) 18.2-r1 (including)
Virtual_traffic_manager Pulsesecure 19.2 (including) 19.2 (including)
Virtual_traffic_manager Pulsesecure 19.2-r1 (including) 19.2-r1 (including)
Virtual_traffic_manager Pulsesecure 19.2-r2 (including) 19.2-r2 (including)
Virtual_traffic_manager Pulsesecure 19.3 (including) 19.3 (including)
Virtual_traffic_manager Pulsesecure 20.1 (including) 20.1 (including)
Virtual_traffic_manager Pulsesecure 20.2 (including) 20.2 (including)
Virtual_traffic_manager Pulsesecure 20.3 (including) 20.3 (including)

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