BIG-IP: Improper Check for Unusual or Exceptional Conditions
CVE-2022-28706 is a high-severity improper check for unusual or exceptional conditions vulnerability in BIG-IP from F5, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 16.1.2, 15.1.5.1 as the first without the flaw, so updating BIG-IP to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.82% chance of exploitation within 30 days, higher than 58% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update BIG-IP to 16.1.2 or 15.1.5.1, whichever matches your release line, or a later version.
- Read the advisory on support.f5.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| F5 | BIG-IP | 16.1.x up to, but not including, 16.1.2; 15.1.x up to, but not including, 15.1.5.1 | 16.1.2, 15.1.5.1 |
| F5 | Big-ip Access Policy Manager | 15.1.0; 15.1.1; 15.1.2; 15.1.3; 15.1.4; 15.1.5; 16.1.0; 16.1.1; and 1 more ranges | Not stated |
| F5 | Big-ip Advanced Firewall Manager | 15.1.0; 15.1.1; 15.1.2; 15.1.3; 15.1.4; 15.1.5; 16.1.0; 16.1.1; and 1 more ranges | Not stated |
| F5 | Big-ip Analytics | 15.1.0; 15.1.1; 15.1.2; 15.1.3; 15.1.4; 15.1.5; 16.1.0; 16.1.1; and 1 more ranges | Not stated |
| F5 | Big-ip Application Acceleration Manager | 15.1.0; 15.1.1; 15.1.2; 15.1.3; 15.1.4; 15.1.5; 16.1.0; 16.1.1; and 1 more ranges | Not stated |
| F5 | Big-ip Application Security Manager | 15.1.0; 15.1.1; 15.1.2; 15.1.3; 15.1.4; 15.1.5; 16.1.0; 16.1.1; and 1 more ranges | Not stated |
| F5 | Big-ip Domain Name System | 15.1.0; 15.1.1; 15.1.2; 15.1.3; 15.1.4; 15.1.5; 16.1.0; 16.1.1; and 1 more ranges | Not stated |
| F5 | Big-ip Fraud Protection Service | 15.1.0; 15.1.1; 15.1.2; 15.1.3; 15.1.4; 15.1.5; 16.1.0; 16.1.1; and 1 more ranges | Not stated |
| F5 | Big-ip Global Traffic Manager | 15.1.0; 15.1.1; 15.1.2; 15.1.3; 15.1.4; 15.1.5; 16.1.0; 16.1.1; and 1 more ranges | Not stated |
| F5 | Big-ip Link Controller | 15.1.0; 15.1.1; 15.1.2; 15.1.3; 15.1.4; 15.1.5; 16.1.0; 16.1.1; and 1 more ranges | Not stated |
| F5 | Big-ip Local Traffic Manager | 15.1.0; 15.1.1; 15.1.2; 15.1.3; 15.1.4; 15.1.5; 16.1.0; 16.1.1; and 1 more ranges | Not stated |
| F5 | Big-ip Policy Enforcement Manager | 15.1.0; 15.1.1; 15.1.2; 15.1.3; 15.1.4; 15.1.5; 16.1.0; 16.1.1; and 1 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
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 5.9 | Medium | CNA (f5.com) |
| CVSS 3.1 | 7.5 | High | NVD |
| CVSS 2.0 | 5.0 | Medium | NVD |
Official description
On F5 BIG-IP 16.1.x versions prior to 16.1.2 and 15.1.x versions prior to 15.1.5.1, when the DNS resolver configuration is used, undisclosed requests can cause the Traffic Management Microkernel (TMM) to terminate. 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: Improper Check for Unusual or Exceptional Conditions
The product does not check or incorrectly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the product.
How developers prevent this class of flaw
- Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Choose languages with features such as exception handling that force the programmer to anticipate unusual conditions that may generate exceptions. Custom exceptions may need to be developed to handle unusual business-logic conditions. Be careful not to pass sensitive exceptions back to the user (CWE-209, CWE-248).
- Check the results of all functions that return a value and verify that the value is expected.
- If using exception handling, catch and throw specific exceptions instead of overly-general exceptions (CWE-396, CWE-397). Catch and handle exceptions as locally as possible so that exceptions do not propagate too far up the call stack (CWE-705). Avoid unchecked or uncaught exceptions where feasible (CWE-248).
More Improper Check for Unusual or Exceptional Conditions vulnerabilities (CWE-754)
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other vulnerabilities in BIG-IP
- 9.8 Critical severity
F5 BIG-IP APM Heap-based Buffer Overflow Exploited
- 8.8 High severity
- 7.5 High severity
- 8.7 High severity
- 8.7 High severity
- 7.5 High severity
Recent Improper Check for Unusual or Exceptional Conditions vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.8 High severity
Red Hat Polkit Incorrect Authorization Exploited
- 7.5 High severity
Spotted an error? Tell us.