CVE Vulnerabilities

CVE-2023-22302

Missing Release of Resource after Effective Lifetime

Published: Feb 01, 2023 | Modified: Nov 07, 2023
CVSS 3.x
5.9
MEDIUM
Source:
NVD
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS 2.x
RedHat/V2
RedHat/V3
Ubuntu

In BIG-IP versions 17.0.x before 17.0.0.2, and 16.1.x beginning in 16.1.2.2 to before 16.1.3.3, when an HTTP profile is configured on a virtual server and conditions beyond the attacker’s control exist on the target pool member, undisclosed requests sent to the BIG-IP system can cause the Traffic Management Microkernel (TMM) to terminate. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

Weakness

The product does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed.

Affected Software

Name Vendor Start Version End Version
Big-ip_advanced_firewall_manager F5 17.0.0 *
Big-ip_access_policy_manager F5 17.0.0 *
Big-ip_policy_enforcement_manager F5 16.1.2.2 *
Big-ip_local_traffic_manager F5 16.1.2.2 *
Big-ip_link_controller F5 16.1.2.2 *
Big-ip_fraud_protection_service F5 16.1.2.2 *
Big-ip_domain_name_system F5 16.1.2.2 *
Big-ip_ddos_hybrid_defender F5 16.1.2.2 *
Big-ip_application_security_manager F5 16.1.2.2 *
Big-ip_access_policy_manager F5 16.1.2.2 *
Big-ip_advanced_firewall_manager F5 16.1.2.2 *
Big-ip_analytics F5 16.1.2.2 *
Big-ip_application_acceleration_manager F5 16.1.2.2 *
Big-ip_ssl_orchestrator F5 16.1.2.2 *
Big-ip_analytics F5 17.0.0 *
Big-ip_application_acceleration_manager F5 17.0.0 *
Big-ip_application_security_manager F5 17.0.0 *
Big-ip_ddos_hybrid_defender F5 17.0.0 *
Big-ip_domain_name_system F5 17.0.0 *
Big-ip_fraud_protection_service F5 17.0.0 *
Big-ip_link_controller F5 17.0.0 *
Big-ip_local_traffic_manager F5 17.0.0 *
Big-ip_policy_enforcement_manager F5 17.0.0 *
Big-ip_ssl_orchestrator F5 17.0.0 *

Potential Mitigations

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
  • For example, languages such as Java, Ruby, and Lisp perform automatic garbage collection that releases memory for objects that have been deallocated.
  • Use resource-limiting settings provided by the operating system or environment. For example, when managing system resources in POSIX, setrlimit() can be used to set limits for certain types of resources, and getrlimit() can determine how many resources are available. However, these functions are not available on all operating systems.
  • When the current levels get close to the maximum that is defined for the application (see CWE-770), then limit the allocation of further resources to privileged users; alternately, begin releasing resources for less-privileged users. While this mitigation may protect the system from attack, it will not necessarily stop attackers from adversely impacting other users.
  • Ensure that the application performs the appropriate error checks and error handling in case resources become unavailable (CWE-703).

References