CVE-2017-7658 (debian_linux, e-series_santricity_management, e-series_santricity_os_controller, e-series_santricity_web_services, hci_management_node, hci_storage_node, jetty, oncommand_system_manager, oncommand_unified_manager_for_7-mode, rest_data_services, retail_xstore_payment, retail_xstore_point_of_service, santricity_cloud_connector, snap_creator_framework, snapcenter, snapmanager, solidfire, storage_services_connector, xp_p9000_command_view)

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.

View Full Alert

Leave a Reply