CyberSecBulletin
CVE-2022-26370NVD status: Modified

BIG-IP: Use of Uninitialized Resource

CVE-2022-26370 is a high-severity use of uninitialized resource 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.2, 15.1.5, 14.1.4.6 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.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update BIG-IP to 16.1.2.2 or 15.1.5 or 14.1.4.6, whichever matches your release line, or a later version.
  2. Read the advisory on support.f5.com for workarounds and exact fixed builds.
  3. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
F5BIG-IP16.1.x up to, but not including, 16.1.2.2; 15.1.x up to, but not including, 15.1.5; 14.1.x up to, but not including, 14.1.4.616.1.2.2, 15.1.5, 14.1.4.6
F5Big-ip Access Policy Manager14.1.0; 14.1.2; 14.1.3; 14.1.4; 15.1.0; 15.1.1; 15.1.2; 15.1.3; and 5 more rangesNot stated
F5Big-ip Advanced Firewall Manager14.1.0; 14.1.2; 14.1.3; 14.1.4; 15.1.0; 15.1.1; 15.1.2; 15.1.3; and 5 more rangesNot stated
F5Big-ip Analytics14.1.0; 14.1.2; 14.1.3; 14.1.4; 15.1.0; 15.1.1; 15.1.2; 15.1.3; and 5 more rangesNot stated
F5Big-ip Application Acceleration Manager14.1.0; 14.1.2; 14.1.3; 14.1.4; 15.1.0; 15.1.1; 15.1.2; 15.1.3; and 5 more rangesNot stated
F5Big-ip Application Security Manager14.1.0; 14.1.2; 14.1.3; 14.1.4; 15.1.0; 15.1.1; 15.1.2; 15.1.3; and 5 more rangesNot stated
F5Big-ip Domain Name System14.1.0; 14.1.2; 14.1.3; 14.1.4; 15.1.0; 15.1.1; 15.1.2; 15.1.3; and 5 more rangesNot stated
F5Big-ip Fraud Protection Service14.1.0; 14.1.2; 14.1.3; 14.1.4; 15.1.0; 15.1.1; 15.1.2; 15.1.3; and 5 more rangesNot stated
F5Big-ip Global Traffic Manager14.1.0; 14.1.2; 14.1.3; 14.1.4; 15.1.0; 15.1.1; 15.1.2; 15.1.3; and 5 more rangesNot stated
F5Big-ip Link Controller14.1.0; 14.1.2; 14.1.3; 14.1.4; 15.1.0; 15.1.1; 15.1.2; 15.1.3; and 5 more rangesNot stated
F5Big-ip Local Traffic Manager14.1.0; 14.1.2; 14.1.3; 14.1.4; 15.1.0; 15.1.1; 15.1.2; 15.1.3; and 5 more rangesNot stated
F5Big-ip Policy Enforcement Manager14.1.0; 14.1.2; 14.1.3; 14.1.4; 15.1.0; 15.1.1; 15.1.2; 15.1.3; and 5 more rangesNot 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 systemScoreSeverityScored by
CVSS 3.15.9MediumCNA (f5.com)
CVSS 3.17.5HighNVD
CVSS 2.05.0MediumNVD

Official description

On F5 BIG-IP 16.1.x versions prior to 16.1.2.2, 15.1.x versions prior to 15.1.5, and 14.1.x versions prior to 14.1.4.6, when a Session Initiation Protocol (SIP) message routing framework (MRF) application layer gateway (ALG) profile is configured on a Message Routing virtual server, 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: Use of Uninitialized Resource

The product uses or accesses a resource that has not been initialized.

How developers prevent this class of flaw

  • Explicitly initialize the resource before use. If this is performed through an API function or standard procedure, follow all required steps.
  • Pay close attention to complex conditionals that affect initialization, since some branches might not perform the initialization.
  • Avoid race conditions (CWE-362) during initialization routines.

More Use of Uninitialized Resource vulnerabilities (CWE-908)

Timeline

  1. CVE record published.
  2. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in BIG-IP

All BIG-IP vulnerabilities

Recent Use of Uninitialized Resource vulnerabilities

Spotted an error? Tell us.