CVE Vulnerabilities

CVE-2017-5647

Exposure of Sensitive Information to an Unauthorized Actor

Published: Apr 17, 2017 | Modified: Dec 08, 2023
CVSS 3.x
7.5
HIGH
Source:
NVD
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CVSS 2.x
5 MEDIUM
AV:N/AC:L/Au:N/C:P/I:N/A:N
RedHat/V2
RedHat/V3
7.5 IMPORTANT
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Ubuntu
MEDIUM

A bug in the handling of the pipelined requests in Apache Tomcat 9.0.0.M1 to 9.0.0.M18, 8.5.0 to 8.5.12, 8.0.0.RC1 to 8.0.42, 7.0.0 to 7.0.76, and 6.0.0 to 6.0.52, when send file was used, results in the pipelined request being lost when send file processing of the previous request completed. This could result in responses appearing to be sent for the wrong request. For example, a user agent that sent requests A, B and C could see the correct response for request A, the response for request C for request B and no response for request C.

Weakness

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

Affected Software

Name Vendor Start Version End Version
Tomcat Apache 6.0.0 (including) 6.0.0 (including)
Tomcat Apache 6.0.1 (including) 6.0.1 (including)
Tomcat Apache 6.0.2 (including) 6.0.2 (including)
Tomcat Apache 6.0.3 (including) 6.0.3 (including)
Tomcat Apache 6.0.4 (including) 6.0.4 (including)
Tomcat Apache 6.0.5 (including) 6.0.5 (including)
Tomcat Apache 6.0.6 (including) 6.0.6 (including)
Tomcat Apache 6.0.7 (including) 6.0.7 (including)
Tomcat Apache 6.0.8 (including) 6.0.8 (including)
Tomcat Apache 6.0.9 (including) 6.0.9 (including)
Tomcat Apache 6.0.10 (including) 6.0.10 (including)
Tomcat Apache 6.0.11 (including) 6.0.11 (including)
Tomcat Apache 6.0.12 (including) 6.0.12 (including)
Tomcat Apache 6.0.13 (including) 6.0.13 (including)
Tomcat Apache 6.0.14 (including) 6.0.14 (including)
Tomcat Apache 6.0.15 (including) 6.0.15 (including)
Tomcat Apache 6.0.16 (including) 6.0.16 (including)
Tomcat Apache 6.0.17 (including) 6.0.17 (including)
Tomcat Apache 6.0.18 (including) 6.0.18 (including)
Tomcat Apache 6.0.19 (including) 6.0.19 (including)
Tomcat Apache 6.0.20 (including) 6.0.20 (including)
Tomcat Apache 6.0.21 (including) 6.0.21 (including)
Tomcat Apache 6.0.22 (including) 6.0.22 (including)
Tomcat Apache 6.0.23 (including) 6.0.23 (including)
Tomcat Apache 6.0.24 (including) 6.0.24 (including)
Tomcat Apache 6.0.25 (including) 6.0.25 (including)
Tomcat Apache 6.0.26 (including) 6.0.26 (including)
Tomcat Apache 6.0.27 (including) 6.0.27 (including)
Tomcat Apache 6.0.28 (including) 6.0.28 (including)
Tomcat Apache 6.0.29 (including) 6.0.29 (including)
Tomcat Apache 6.0.30 (including) 6.0.30 (including)
Tomcat Apache 6.0.31 (including) 6.0.31 (including)
Tomcat Apache 6.0.32 (including) 6.0.32 (including)
Tomcat Apache 6.0.33 (including) 6.0.33 (including)
Tomcat Apache 6.0.34 (including) 6.0.34 (including)
Tomcat Apache 6.0.35 (including) 6.0.35 (including)
Tomcat Apache 6.0.36 (including) 6.0.36 (including)
Tomcat Apache 6.0.37 (including) 6.0.37 (including)
Tomcat Apache 6.0.38 (including) 6.0.38 (including)
Tomcat Apache 6.0.39 (including) 6.0.39 (including)
Tomcat Apache 6.0.40 (including) 6.0.40 (including)
Tomcat Apache 6.0.41 (including) 6.0.41 (including)
Tomcat Apache 6.0.42 (including) 6.0.42 (including)
Tomcat Apache 6.0.43 (including) 6.0.43 (including)
Tomcat Apache 6.0.44 (including) 6.0.44 (including)
Tomcat Apache 6.0.45 (including) 6.0.45 (including)
Tomcat Apache 6.0.46 (including) 6.0.46 (including)
Tomcat Apache 6.0.47 (including) 6.0.47 (including)
Tomcat Apache 6.0.48 (including) 6.0.48 (including)
Tomcat Apache 6.0.49 (including) 6.0.49 (including)
Tomcat Apache 6.0.50 (including) 6.0.50 (including)
Tomcat Apache 6.0.51 (including) 6.0.51 (including)
Tomcat Apache 6.0.52 (including) 6.0.52 (including)
Red Hat Enterprise Linux 6 RedHat tomcat6-0:6.0.24-111.el6_9 *
Red Hat Enterprise Linux 7 RedHat tomcat-0:7.0.76-3.el7_4 *
Red Hat JBoss Enterprise Web Server 2 for RHEL 6 RedHat jbcs-httpd24-openssl-1:1.0.2h-13.jbcs.el6 *
Red Hat JBoss Enterprise Web Server 2 for RHEL 6 RedHat tomcat6-0:6.0.41-17_patch_04.ep6.el6 *
Red Hat JBoss Enterprise Web Server 2 for RHEL 6 RedHat tomcat7-0:7.0.54-25_patch_05.ep6.el6 *
Red Hat JBoss Enterprise Web Server 2 for RHEL 7 RedHat jbcs-httpd24-openssl-1:1.0.2h-13.jbcs.el7 *
Red Hat JBoss Enterprise Web Server 2 for RHEL 7 RedHat tomcat6-0:6.0.41-17_patch_04.ep6.el7 *
Red Hat JBoss Enterprise Web Server 2 for RHEL 7 RedHat tomcat7-0:7.0.54-25_patch_05.ep6.el7 *
Red Hat JBoss Web Server 2.1 RedHat tomcat6 *
Red Hat JBoss Web Server 2.1 RedHat tomcat7 *
Red Hat JBoss Web Server 3.1 RedHat *
Red Hat JBoss Web Server 3 for RHEL 6 RedHat log4j-eap6-0:1.2.16-12.redhat_3.1.ep6.el6 *
Red Hat JBoss Web Server 3 for RHEL 6 RedHat tomcat7-0:7.0.70-22.ep7.el6 *
Red Hat JBoss Web Server 3 for RHEL 6 RedHat tomcat8-0:8.0.36-24.ep7.el6 *
Red Hat JBoss Web Server 3 for RHEL 6 RedHat tomcat-native-0:1.2.8-10.redhat_10.ep7.el6 *
Red Hat JBoss Web Server 3 for RHEL 7 RedHat log4j-eap6-0:1.2.16-12.redhat_3.1.ep6.el7 *
Red Hat JBoss Web Server 3 for RHEL 7 RedHat tomcat7-0:7.0.70-22.ep7.el7 *
Red Hat JBoss Web Server 3 for RHEL 7 RedHat tomcat8-0:8.0.36-24.ep7.el7 *
Red Hat JBoss Web Server 3 for RHEL 7 RedHat tomcat-native-0:1.2.8-10.redhat_10.ep7.el7 *
Tomcat6 Ubuntu esm-infra-legacy/trusty *
Tomcat6 Ubuntu precise *
Tomcat6 Ubuntu precise/esm *
Tomcat6 Ubuntu trusty *
Tomcat6 Ubuntu trusty/esm *
Tomcat6 Ubuntu upstream *
Tomcat7 Ubuntu esm-apps/xenial *
Tomcat7 Ubuntu precise *
Tomcat7 Ubuntu trusty *
Tomcat7 Ubuntu upstream *
Tomcat7 Ubuntu xenial *
Tomcat7 Ubuntu yakkety *
Tomcat8 Ubuntu upstream *
Tomcat8 Ubuntu xenial *
Tomcat8 Ubuntu yakkety *
Tomcat8 Ubuntu zesty *

Extended Description

There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker. Some kinds of sensitive information include:

Information might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected. These parties include:

Information exposures can occur in different ways:

It is common practice to describe any loss of confidentiality as an “information exposure,” but this can lead to overuse of CWE-200 in CWE mapping. From the CWE perspective, loss of confidentiality is a technical impact that can arise from dozens of different weaknesses, such as insecure file permissions or out-of-bounds read. CWE-200 and its lower-level descendants are intended to cover the mistakes that occur in behaviors that explicitly manage, store, transfer, or cleanse sensitive information.

Potential Mitigations

  • Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
  • Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References