CVE Vulnerabilities

CVE-2016-5388

Improper Access Control

Published: Jul 19, 2016 | Modified: Feb 12, 2023
CVSS 3.x
8.1
HIGH
Source:
NVD
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
5.1 MEDIUM
AV:N/AC:H/Au:N/C:P/I:P/A:P
RedHat/V2
RedHat/V3
Ubuntu

Apache Tomcat 7.x through 7.0.70 and 8.x through 8.5.4, when the CGI Servlet is enabled, follows RFC 3875 section 4.1.18 and therefore does not protect applications from the presence of untrusted client data in the HTTP_PROXY environment variable, which might allow remote attackers to redirect an applications outbound HTTP traffic to an arbitrary proxy server via a crafted Proxy header in an HTTP request, aka an httpoxy issue. NOTE: the vendor states A mitigation is planned for future releases of Tomcat, tracked as CVE-2016-5388; in other words, this is not a CVE ID for a vulnerability.

Weakness

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

Affected Software

Name Vendor Start Version End Version
Enterprise_linux_desktop Redhat 7.0 7.0
Enterprise_linux_server_aus Redhat 7.2 7.2
Enterprise_linux_workstation Redhat 7.0 7.0
Enterprise_linux_server_tus Redhat 7.2 7.2
Enterprise_linux_server Redhat 7.0 7.0
Enterprise_linux_hpc_node Redhat 7.0 7.0
Enterprise_linux_server_eus Redhat 7.2 7.2
Enterprise_linux_hpc_node_eus Redhat 7.2 7.2

Extended Description

Access control involves the use of several protection mechanisms such as:

When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses:

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