CVE Vulnerabilities

CVE-2024-41723

Exposure of Sensitive Information to an Unauthorized Actor

Published: Aug 14, 2024 | Modified: Aug 20, 2024
CVSS 3.x
4.3
MEDIUM
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
CVSS 2.x
RedHat/V2
RedHat/V3
Ubuntu

Undisclosed requests to BIG-IP iControl REST can lead to information leak of user account names.  Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

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
Big-ip_access_policy_manager F5 15.1.0 (including) 15.1.1 (including)
Big-ip_access_policy_manager F5 16.1.0 (including) 16.1.5 (excluding)
Big-ip_access_policy_manager F5 17.1.0 (including) 17.1.0 (including)
Big-ip_advanced_firewall_manager F5 15.1.0 (including) 15.1.1 (including)
Big-ip_advanced_firewall_manager F5 16.1.0 (including) 16.1.5 (excluding)
Big-ip_advanced_firewall_manager F5 17.1.0 (including) 17.1.0 (including)
Big-ip_advanced_web_application_firewall F5 15.1.0 (including) 15.1.1 (including)
Big-ip_advanced_web_application_firewall F5 16.1.0 (including) 16.1.5 (excluding)
Big-ip_advanced_web_application_firewall F5 17.1.0 (including) 17.1.0 (including)
Big-ip_analytics F5 15.1.0 (including) 15.1.1 (including)
Big-ip_analytics F5 16.1.0 (including) 16.1.5 (excluding)
Big-ip_analytics F5 17.1.0 (including) 17.1.0 (including)
Big-ip_application_acceleration_manager F5 15.1.0 (including) 15.1.1 (including)
Big-ip_application_acceleration_manager F5 16.1.0 (including) 16.1.5 (excluding)
Big-ip_application_acceleration_manager F5 17.1.0 (including) 17.1.0 (including)
Big-ip_application_security_manager F5 15.1.0 (including) 15.1.1 (including)
Big-ip_application_security_manager F5 16.1.0 (including) 16.1.5 (excluding)
Big-ip_application_security_manager F5 17.1.0 (including) 17.1.0 (including)
Big-ip_application_visibility_and_reporting F5 15.1.0 (including) 15.1.1 (including)
Big-ip_application_visibility_and_reporting F5 16.1.0 (including) 16.1.5 (excluding)
Big-ip_application_visibility_and_reporting F5 17.1.0 (including) 17.1.0 (including)
Big-ip_automation_toolchain F5 15.1.0 (including) 15.1.1 (including)
Big-ip_automation_toolchain F5 16.1.0 (including) 16.1.5 (excluding)
Big-ip_automation_toolchain F5 17.1.0 (including) 17.1.0 (including)
Big-ip_carrier-grade_nat F5 15.1.0 (including) 15.1.1 (including)
Big-ip_carrier-grade_nat F5 16.1.0 (including) 16.1.5 (excluding)
Big-ip_carrier-grade_nat F5 17.1.0 (including) 17.1.0 (including)
Big-ip_container_ingress_services F5 15.1.0 (including) 15.1.1 (including)
Big-ip_container_ingress_services F5 16.1.0 (including) 16.1.5 (excluding)
Big-ip_container_ingress_services F5 17.1.0 (including) 17.1.0 (including)
Big-ip_ddos_hybrid_defender F5 15.1.0 (including) 15.1.1 (including)
Big-ip_ddos_hybrid_defender F5 16.1.0 (including) 16.1.5 (excluding)
Big-ip_ddos_hybrid_defender F5 17.1.0 (including) 17.1.0 (including)
Big-ip_domain_name_system F5 15.1.0 (including) 15.1.1 (including)
Big-ip_domain_name_system F5 16.1.0 (including) 16.1.5 (excluding)
Big-ip_domain_name_system F5 17.1.0 (including) 17.1.0 (including)
Big-ip_edge_gateway F5 15.1.0 (including) 15.1.1 (including)
Big-ip_edge_gateway F5 16.1.0 (including) 16.1.5 (excluding)
Big-ip_edge_gateway F5 17.1.0 (including) 17.1.0 (including)
Big-ip_fraud_protection_service F5 15.1.0 (including) 15.1.1 (including)
Big-ip_fraud_protection_service F5 16.1.0 (including) 16.1.5 (excluding)
Big-ip_fraud_protection_service F5 17.1.0 (including) 17.1.0 (including)
Big-ip_global_traffic_manager F5 15.1.0 (including) 15.1.1 (including)
Big-ip_global_traffic_manager F5 16.1.0 (including) 16.1.5 (excluding)
Big-ip_global_traffic_manager F5 17.1.0 (including) 17.1.0 (including)
Big-ip_link_controller F5 15.1.0 (including) 15.1.1 (including)
Big-ip_link_controller F5 16.1.0 (including) 16.1.5 (excluding)
Big-ip_link_controller F5 17.1.0 (including) 17.1.0 (including)
Big-ip_local_traffic_manager F5 15.1.0 (including) 15.1.1 (including)
Big-ip_local_traffic_manager F5 16.1.0 (including) 16.1.5 (excluding)
Big-ip_local_traffic_manager F5 17.1.0 (including) 17.1.0 (including)
Big-ip_policy_enforcement_manager F5 15.1.0 (including) 15.1.1 (including)
Big-ip_policy_enforcement_manager F5 16.1.0 (including) 16.1.5 (excluding)
Big-ip_policy_enforcement_manager F5 17.1.0 (including) 17.1.0 (including)
Big-ip_ssl_orchestrator F5 15.1.0 (including) 15.1.1 (including)
Big-ip_ssl_orchestrator F5 16.1.0 (including) 16.1.5 (excluding)
Big-ip_ssl_orchestrator F5 17.1.0 (including) 17.1.0 (including)
Big-ip_webaccelerator F5 15.1.0 (including) 15.1.1 (including)
Big-ip_webaccelerator F5 16.1.0 (including) 16.1.5 (excluding)
Big-ip_webaccelerator F5 17.1.0 (including) 17.1.0 (including)
Big-ip_websafe F5 15.1.0 (including) 15.1.1 (including)
Big-ip_websafe F5 16.1.0 (including) 16.1.5 (excluding)
Big-ip_websafe F5 17.1.0 (including) 17.1.0 (including)

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