CVE Vulnerabilities

CVE-2022-29263

Incorrect Permission Assignment for Critical Resource

Published: May 05, 2022 | Modified: May 12, 2022
CVSS 3.x
7.8
HIGH
Source:
NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
4.6 MEDIUM
AV:L/AC:L/Au:N/C:P/I:P/A:P
RedHat/V2
RedHat/V3
Ubuntu

On F5 BIG-IP APM 16.1.x versions prior to 16.1.2.2, 15.1.x versions prior to 15.1.5.1, 14.1.x versions prior to 14.1.4.6, 13.1.x versions prior to 13.1.5, and all versions of 12.1.x and 11.6.x, as well as F5 BIG-IP APM Clients 7.x versions prior to 7.2.1.5, the BIG-IP Edge Client Component Installer Service does not use best practice while saving temporary files. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated

Weakness

The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.

Affected Software

Name Vendor Start Version End Version
Access_policy_manager_clients F5 7.1.8 (including) 7.1.8 (including)
Access_policy_manager_clients F5 7.1.8.5 (including) 7.1.8.5 (including)
Access_policy_manager_clients F5 7.1.9 (including) 7.1.9 (including)
Access_policy_manager_clients F5 7.1.9.7 (including) 7.1.9.7 (including)
Access_policy_manager_clients F5 7.1.9.8 (including) 7.1.9.8 (including)
Access_policy_manager_clients F5 7.2.1 (including) 7.2.1 (including)
Access_policy_manager_clients F5 7.2.1.1 (including) 7.2.1.1 (including)
Big-ip_access_policy_manager F5 11.6.1 (including) 11.6.1 (including)
Big-ip_access_policy_manager F5 11.6.2 (including) 11.6.2 (including)
Big-ip_access_policy_manager F5 11.6.3 (including) 11.6.3 (including)
Big-ip_access_policy_manager F5 11.6.4 (including) 11.6.4 (including)
Big-ip_access_policy_manager F5 11.6.5 (including) 11.6.5 (including)
Big-ip_access_policy_manager F5 12.1.0 (including) 12.1.0 (including)
Big-ip_access_policy_manager F5 12.1.1 (including) 12.1.1 (including)
Big-ip_access_policy_manager F5 12.1.2 (including) 12.1.2 (including)
Big-ip_access_policy_manager F5 12.1.3 (including) 12.1.3 (including)
Big-ip_access_policy_manager F5 12.1.4 (including) 12.1.4 (including)
Big-ip_access_policy_manager F5 12.1.5 (including) 12.1.5 (including)
Big-ip_access_policy_manager F5 12.1.6 (including) 12.1.6 (including)
Big-ip_access_policy_manager F5 13.1.0 (including) 13.1.0 (including)
Big-ip_access_policy_manager F5 13.1.1 (including) 13.1.1 (including)
Big-ip_access_policy_manager F5 13.1.3 (including) 13.1.3 (including)
Big-ip_access_policy_manager F5 13.1.4 (including) 13.1.4 (including)
Big-ip_access_policy_manager F5 13.1.5 (including) 13.1.5 (including)
Big-ip_access_policy_manager F5 14.1.0 (including) 14.1.0 (including)
Big-ip_access_policy_manager F5 14.1.2 (including) 14.1.2 (including)
Big-ip_access_policy_manager F5 14.1.3 (including) 14.1.3 (including)
Big-ip_access_policy_manager F5 14.1.4 (including) 14.1.4 (including)
Big-ip_access_policy_manager F5 15.1.0 (including) 15.1.0 (including)
Big-ip_access_policy_manager F5 15.1.1 (including) 15.1.1 (including)
Big-ip_access_policy_manager F5 15.1.2 (including) 15.1.2 (including)
Big-ip_access_policy_manager F5 15.1.3 (including) 15.1.3 (including)
Big-ip_access_policy_manager F5 15.1.4 (including) 15.1.4 (including)
Big-ip_access_policy_manager F5 15.1.5 (including) 15.1.5 (including)
Big-ip_access_policy_manager F5 16.1.0 (including) 16.1.0 (including)
Big-ip_access_policy_manager F5 16.1.1 (including) 16.1.1 (including)
Big-ip_access_policy_manager F5 16.1.2 (including) 16.1.2 (including)
Big-ip_access_policy_manager F5 17.0.0 (including) 17.0.0 (including)

Potential Mitigations

  • Run the code in a “jail” or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software.
  • OS-level examples include the Unix chroot jail, AppArmor, and SELinux. In general, managed code may provide some protection. For example, java.io.FilePermission in the Java SecurityManager allows the software to specify restrictions on file operations.
  • This may not be a feasible solution, and it only limits the impact to the operating system; the rest of the application may still be subject to compromise.
  • Be careful to avoid CWE-243 and other weaknesses related to jails.

References