CyberSecBulletin
CVE-2022-23012NVD status: Modified

BIG-IP: Double Free

CVE-2022-23012 is a high-severity double free vulnerability in BIG-IP, 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. Affected BIG-IP versions: 15.1.x before 15.1.4.1 and 14.1.x before 14.1.4.5. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.92% chance of exploitation within 30 days, higher than 61% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Big-ip Access Policy Manager to 14.1.4.5 or 15.1.4.1, whichever matches your release line, or a later version.
  2. Update Big-ip Advanced Firewall Manager to 14.1.4.5 or 15.1.4.1, whichever matches your release line, or a later version.
  3. Update Big-ip Analytics to 14.1.4.5 or 15.1.4.1, whichever matches your release line, or a later version.
  4. Read the advisory on support.f5.com for workarounds and exact fixed builds.
  5. 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
BIG-IPBIG-IP15.1.x before 15.1.4.1 and 14.1.x before 14.1.4.5Not stated
F5Big-ip Access Policy Manager14.1.0 up to, but not including, 14.1.4.5; 15.1.0 up to, but not including, 15.1.4.114.1.4.5, 15.1.4.1
F5Big-ip Advanced Firewall Manager14.1.0 up to, but not including, 14.1.4.5; 15.1.0 up to, but not including, 15.1.4.114.1.4.5, 15.1.4.1
F5Big-ip Analytics14.1.0 up to, but not including, 14.1.4.5; 15.1.0 up to, but not including, 15.1.4.114.1.4.5, 15.1.4.1
F5Big-ip Application Acceleration Manager14.1.0 up to, but not including, 14.1.4.5; 15.1.0 up to, but not including, 15.1.4.114.1.4.5, 15.1.4.1
F5Big-ip Application Security Manager14.1.0 up to, but not including, 14.1.4.5; 15.1.0 up to, but not including, 15.1.4.114.1.4.5, 15.1.4.1
F5Big-ip Domain Name System14.1.0 up to, but not including, 14.1.4.5; 15.1.0 up to, but not including, 15.1.4.114.1.4.5, 15.1.4.1
F5Big-ip Fraud Protection Service14.1.0 up to, but not including, 14.1.4.5; 15.1.0 up to, but not including, 15.1.4.114.1.4.5, 15.1.4.1
F5Big-ip Global Traffic Manager14.1.0 up to, but not including, 14.1.4.5; 15.1.0 up to, but not including, 15.1.4.114.1.4.5, 15.1.4.1
F5Big-ip Link Controller14.1.0 up to, but not including, 14.1.4.5; 15.1.0 up to, but not including, 15.1.4.114.1.4.5, 15.1.4.1
F5Big-ip Local Traffic Manager14.1.0 up to, but not including, 14.1.4.5; 15.1.0 up to, but not including, 15.1.4.114.1.4.5, 15.1.4.1
F5Big-ip Policy Enforcement Manager14.1.0 up to, but not including, 14.1.4.5; 15.1.0 up to, but not including, 15.1.4.114.1.4.5, 15.1.4.1

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.17.5HighNVD
CVSS 2.07.1HighNVD

Official description

On BIG-IP versions 15.1.x before 15.1.4.1 and 14.1.x before 14.1.4.5, when the HTTP/2 profile is configured on a 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: Double Free

The product calls free() twice on the same memory address.

How developers prevent this class of flaw

  • Choose a language that provides automatic memory management.
  • Ensure that each allocation is freed only once. After freeing a chunk, set the pointer to NULL to ensure the pointer cannot be freed again. In complicated error conditions, be sure that clean-up routines respect the state of allocation properly. If the language is object oriented, ensure that object destructors delete each chunk of memory only once.
  • Use a static analysis tool to find double free instances.

More Double Free vulnerabilities (CWE-415)

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 Double Free vulnerabilities

Spotted an error? Tell us.