CVE Vulnerabilities

CVE-2016-7468

Improper Access Control

Published: Mar 23, 2017 | Modified: Jun 06, 2019
CVSS 3.x
5.9
MEDIUM
Source:
NVD
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS 2.x
4.3 MEDIUM
AV:N/AC:M/Au:N/C:N/I:N/A:P
RedHat/V2
RedHat/V3
Ubuntu

An unauthenticated remote attacker may be able to disrupt services on F5 BIG-IP 11.4.1 - 11.5.4 devices with maliciously crafted network traffic. This vulnerability affects virtual servers associated with TCP profiles when the BIG-IP systems tm.tcpprogressive db variable value is set to non-default setting enabled. The default value for the tm.tcpprogressive db variable is negotiate. An attacker may be able to disrupt traffic or cause the BIG-IP system to fail over to another device in the device group.

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_local_traffic_manager F5 11.4.1 11.4.1
Big-ip_local_traffic_manager F5 11.5.4 11.5.4
Big-ip_local_traffic_manager F5 11.5.1 11.5.1
Big-ip_local_traffic_manager F5 11.5.2 11.5.2
Big-ip_local_traffic_manager F5 11.5.3 11.5.3
Big-ip_local_traffic_manager F5 11.5.0 11.5.0
Big-ip_local_traffic_manager F5 11.4.0 11.4.0

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