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 encoding header, the content-length was ignored (as per RFC 2616). If an intermediary decided on the shorter length, but still passed on the longer body, then body content could be interpreted by Jetty as a pipelined request. If the intermediary was imposing authorization, the fake pipelined request would bypass that authorization.
References
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
Configuration 3 (hide)
|
Configuration 4 (hide)
AND |
|
Configuration 5 (hide)
|
History
07 Nov 2023, 02:50
Type | Values Removed | Values Added |
---|---|---|
References |
|
|
Information
Published : 2018-06-26 17:29
Updated : 2024-02-28 16:25
NVD link : CVE-2017-7658
Mitre link : CVE-2017-7658
CVE.ORG link : CVE-2017-7658
JSON object : View
Products Affected
netapp
- oncommand_system_manager
- solidfire
- hci_storage_node
- e-series_santricity_management
- snap_creator_framework
- e-series_santricity_os_controller
- storage_services_connector
- oncommand_unified_manager_for_7-mode
- snapmanager
- snapcenter
- hci_management_node
- e-series_santricity_web_services
- santricity_cloud_connector
oracle
- rest_data_services
- retail_xstore_point_of_service
- retail_xstore_payment
eclipse
- jetty
hp
- xp_p9000
- xp_p9000_command_view
debian
- debian_linux
CWE
CWE-444
Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')