CVE Vulnerabilities

CVE-2021-23015

Incorrect Authorization

Published: May 10, 2021 | Modified: May 24, 2021
CVSS 3.x
7.2
HIGH
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
6.5 MEDIUM
AV:N/AC:L/Au:S/C:P/I:P/A:P
RedHat/V2
RedHat/V3
Ubuntu

On BIG-IP 15.1.x before 15.1.3, 14.1.x before 14.1.4.2, 13.1.0.8 through 13.1.3.6, and all versions of 16.0.x, when running in Appliance Mode, an authenticated user assigned the Administrator role may be able to bypass Appliance Mode restrictions utilizing undisclosed iControl REST endpoints. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

Weakness

The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions.

Affected Software

Name Vendor Start Version End Version
Big-ip_access_policy_manager F5 16.0.0 *
Big-ip_advanced_firewall_manager F5 16.0.0 *
Big-ip_application_acceleration_manager F5 16.0.0 *
Big-ip_analytics F5 16.0.0 *
Big-ip_application_security_manager F5 16.0.0 *
Big-ip_domain_name_system F5 16.0.0 *
Big-ip_global_traffic_manager F5 16.0.0 *
Big-ip_fraud_protection_service F5 16.0.0 *
Big-ip_link_controller F5 16.0.0 *
Big-ip_local_traffic_manager F5 16.0.0 *
Big-ip_policy_enforcement_manager F5 16.0.0 *
Big-ip_advanced_web_application_firewall F5 16.0.0 *
Big-ip_ddos_hybrid_defender F5 16.0.0 *
Big-ip_ssl_orchestrator F5 16.0.0 *
Big-ip_application_acceleration_manager F5 14.1.0 *
Big-ip_local_traffic_manager F5 14.1.0 *
Big-ip_advanced_firewall_manager F5 14.1.0 *
Big-ip_analytics F5 14.1.0 *
Big-ip_application_security_manager F5 14.1.0 *
Big-ip_access_policy_manager F5 14.1.0 *
Big-ip_ddos_hybrid_defender F5 14.1.0 *
Big-ip_domain_name_system F5 14.1.0 *
Big-ip_fraud_protection_service F5 14.1.0 *
Big-ip_global_traffic_manager F5 14.1.0 *
Big-ip_link_controller F5 14.1.0 *
Big-ip_policy_enforcement_manager F5 14.1.0 *
Big-ip_access_policy_manager F5 13.1.0 *
Big-ip_access_policy_manager F5 15.1.0 *
Big-ip_application_security_manager F5 15.1.0 *
Big-ip_advanced_web_application_firewall F5 14.1.0 14.1.4
Big-ip_advanced_firewall_manager F5 15.1.0 *
Big-ip_advanced_web_application_firewall F5 15.1.0 *
Big-ip_analytics F5 15.1.0 *
Big-ip_application_acceleration_manager F5 15.1.0 *
Big-ip_ddos_hybrid_defender F5 15.1.0 *
Big-ip_domain_name_system F5 15.1.0 *
Big-ip_fraud_protection_service F5 15.1.0 *
Big-ip_global_traffic_manager F5 15.1.0 *
Big-ip_link_controller F5 15.1.0 *
Big-ip_local_traffic_manager F5 15.1.0 *
Big-ip_policy_enforcement_manager F5 15.1.0 *
Big-ip_ssl_orchestrator F5 15.1.0 *
Big-ip_advanced_firewall_manager F5 13.1.0 *
Big-ip_advanced_web_application_firewall F5 13.1.0 *
Big-ip_analytics F5 13.1.0 *
Big-ip_application_acceleration_manager F5 13.1.0 *
Big-ip_application_security_manager F5 13.1.0 *
Big-ip_ddos_hybrid_defender F5 13.1.0 *
Big-ip_domain_name_system F5 13.1.0 *
Big-ip_fraud_protection_service F5 13.1.0 *
Big-ip_global_traffic_manager F5 13.1.0 *
Big-ip_link_controller F5 13.1.0 *
Big-ip_local_traffic_manager F5 13.1.0 *
Big-ip_policy_enforcement_manager F5 13.1.0 *
Big-ip_ssl_orchestrator F5 13.1.0 *
Big-ip_ssl_orchestrator F5 14.1.0 *

Extended Description

Assuming a user with a given identity, authorization is the process of determining whether that user can access a given resource, based on the user’s privileges and any permissions or other access-control specifications that apply to the resource. When access control checks are incorrectly applied, users are able to access data or perform actions that they should not be allowed to perform. This can lead to a wide range of problems, including information exposures, denial of service, and arbitrary code execution.

Potential Mitigations

  • Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries.
  • Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
  • For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
  • For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page.
  • One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.

References