CVE Vulnerabilities

CVE-2016-5700

Improper Access Control

Published: Oct 03, 2016 | Modified: Nov 28, 2016
CVSS 3.x
9.8
CRITICAL
Source:
NVD
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
9.3 HIGH
AV:N/AC:M/Au:N/C:C/I:C/A:C
RedHat/V2
RedHat/V3
Ubuntu

Virtual servers in F5 BIG-IP systems 11.5.0, 11.5.1 before HF11, 11.5.2, 11.5.3, 11.5.4 before HF2, 11.6.0 before HF8, 11.6.1 before HF1, 12.0.0 before HF4, and 12.1.0 before HF2, when configured with the HTTP Explicit Proxy functionality or SOCKS profile, allow remote attackers to modify the system configuration, read system files, and possibly execute arbitrary code via unspecified vectors.

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
Big-ip_policy_enforcement_manager F5 11.5.0 (including) 11.5.0 (including)
Big-ip_policy_enforcement_manager F5 11.5.1 (including) 11.5.1 (including)
Big-ip_policy_enforcement_manager F5 11.5.2 (including) 11.5.2 (including)
Big-ip_policy_enforcement_manager F5 11.5.3 (including) 11.5.3 (including)
Big-ip_policy_enforcement_manager F5 11.5.4 (including) 11.5.4 (including)
Big-ip_policy_enforcement_manager F5 11.6.0 (including) 11.6.0 (including)
Big-ip_policy_enforcement_manager F5 11.6.1 (including) 11.6.1 (including)
Big-ip_policy_enforcement_manager F5 12.0.0 (including) 12.0.0 (including)
Big-ip_policy_enforcement_manager F5 12.1.0 (including) 12.1.0 (including)

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