BIG-IP APM: Incorrect Permission Assignment for Critical Resource
CVE-2022-29263 is a high-severity incorrect permission assignment for critical resource vulnerability in BIG-IP APM from F5, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions 16.1.2.2, 15.1.5.1, 14.1.4.6 as the first without the flaw, so updating BIG-IP APM to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.21% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update BIG-IP APM to 16.1.2.2 or 15.1.5.1 or 14.1.4.6 or 13.1.5, whichever matches your release line, or a later version.
- Update BIG-IP APM Clients to 7.2.1.5 or a later version.
- Read the advisory on support.f5.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| F5 | BIG-IP APM | 12.1.x; 11.6.x; 16.1.x up to, but not including, 16.1.2.2; 15.1.x up to, but not including, 15.1.5.1; 14.1.x up to, but not including, 14.1.4.6; 13.1.x up to, but not including, 13.1.5 | 16.1.2.2, 15.1.5.1, 14.1.4.6, 13.1.5 |
| F5 | BIG-IP APM Clients | 7.x up to, but not including, 7.2.1.5 | 7.2.1.5 |
| F5 | Access Policy Manager Clients | 7.1.8; 7.1.8.5; 7.1.9; 7.1.9.7; 7.1.9.8; 7.2.1; 7.2.1.1 | Not stated |
| F5 | Big-ip Access Policy Manager | 11.6.1; 11.6.2; 11.6.3; 11.6.4; 11.6.5; 12.1.0; 12.1.1; 12.1.2; and 23 more ranges | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.8 | High | CNA (f5.com) |
| CVSS 3.1 | 7.8 | High | NVD |
| CVSS 2.0 | 4.6 | Medium | NVD |
Official description
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
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Incorrect Permission Assignment for Critical Resource
The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
How developers prevent this class of flaw
- When using a critical resource such as a configuration file, check to see if the resource has insecure permissions (such as being modifiable by any regular user), and generate an error or even exit the software if there is a possibility that the resource could have been modified by an unauthorized party.
- Divide the software into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully defining distinct user groups, privileges, and/or roles. Map these against data, functionality, and the related resources. Then set the permissions accordingly. This will allow you to maintain more fine-grained control over your resources.
- During program startup, explicitly set the default permissions or umask to the most restrictive setting possible. Also set the appropriate permissions during program installation. This will prevent you from inheriting insecure permissions from any user who installs or runs the program.
More Incorrect Permission Assignment for Critical Resource vulnerabilities (CWE-732)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other vulnerabilities in BIG-IP APM
- 7.5 High severity
- 7.5 High severity
- 7.7 High severity
- 7.8 High severity
- 7.2 High severity
Recent Incorrect Permission Assignment for Critical Resource vulnerabilities
- 7.3 High severity
- 8.1 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.