CVE-2019-10247 (autovue, communications_analytics, communications_element_manager, communications_services_gatekeeper, communications_session_report_manager, communications_session_route_manager, data_integrator, element, endeca_information_discovery_integrator, enterprise_manager_base_platform, flexcube_core_banking, flexcube_private_banking, hospitality_guest_access, jetty, oncommand_system_manager, retail_xstore_point_of_service, snap_creator_framework, snapcenter, snapmanager, storage_replication_adapter_for_clustered_data_ontap, storage_services_connector, unified_directory, vasa_provider_for_clustered_data_ontap, virtual_storage_console)

In Eclipse Jetty version 7.x, 8.x, 9.2.27 and older, 9.3.26 and older, and 9.4.16 and older, the server running on any OS and Jetty version combination will reveal the configured fully qualified directory base resource location on the output of the 404 error for not finding a Context that matches the requested path. The default server behavior on jetty-distribution and jetty-home will include at the end of the Handler tree a DefaultHandler, which is responsible for reporting this 404 error, it presents the various configured contexts as HTML for users to click through to. This produced HTML includes output that contains the configured fully qualified directory base resource location for each context.

View Full Alert

Leave a Reply