CyberSecBulletin
CVE-2022-26517NVD status: Modified

BIG-IP: Incorrect Calculation

CVE-2022-26517 is a high-severity incorrect calculation 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 15.1.5.1, 14.1.4.6, 13.1.5 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 15.1.5.1 or 14.1.4.6 or 13.1.5, 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-IP15.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.515.1.5.1, 14.1.4.6, 13.1.5
F5Big-ip Access Policy Manager13.1.0; 13.1.1; 13.1.3; 13.1.4; 13.1.5; 14.1.0; 14.1.2; 14.1.3; and 10 more rangesNot stated
F5Big-ip Advanced Firewall Manager13.1.0; 13.1.1; 13.1.3; 13.1.4; 13.1.5; 14.1.0; 14.1.2; 14.1.3; and 10 more rangesNot stated
F5Big-ip Analytics13.1.0; 13.1.1; 13.1.3; 13.1.4; 13.1.5; 14.1.0; 14.1.2; 14.1.3; and 10 more rangesNot stated
F5Big-ip Application Acceleration Manager13.1.0; 13.1.1; 13.1.3; 13.1.4; 13.1.5; 14.1.0; 14.1.2; 14.1.3; and 10 more rangesNot stated
F5Big-ip Application Security Manager13.1.0; 13.1.1; 13.1.3; 13.1.4; 13.1.5; 14.1.0; 14.1.2; 14.1.3; and 10 more rangesNot stated
F5Big-ip Domain Name System13.1.0; 13.1.1; 13.1.3; 13.1.4; 13.1.5; 14.1.0; 14.1.2; 14.1.3; and 10 more rangesNot stated
F5Big-ip Fraud Protection Service13.1.0; 13.1.1; 13.1.3; 13.1.4; 13.1.5; 14.1.0; 14.1.2; 14.1.3; and 10 more rangesNot stated
F5Big-ip Global Traffic Manager13.1.0; 13.1.1; 13.1.3; 13.1.4; 13.1.5; 14.1.0; 14.1.2; 14.1.3; and 10 more rangesNot stated
F5Big-ip Link Controller13.1.0; 13.1.1; 13.1.3; 13.1.4; 13.1.5; 14.1.0; 14.1.2; 14.1.3; and 10 more rangesNot stated
F5Big-ip Local Traffic Manager13.1.0; 13.1.1; 13.1.3; 13.1.4; 13.1.5; 14.1.0; 14.1.2; 14.1.3; and 10 more rangesNot stated
F5Big-ip Policy Enforcement Manager13.1.0; 13.1.1; 13.1.3; 13.1.4; 13.1.5; 14.1.0; 14.1.2; 14.1.3; and 10 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 15.1.x versions prior to 15.1.5.1, 14.1.x versions prior to 14.1.4.6, and 13.1.x versions prior to 13.1.5, when the BIG-IP CGNAT Large Scale NAT (LSN) pool is configured on a virtual server and packet filtering is enabled, 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: Incorrect Calculation

The product performs a calculation that generates incorrect or unintended results that are later used in security-critical decisions or resource management.

How developers prevent this class of flaw

  • Understand your programming language's underlying representation and how it interacts with numeric calculation. Pay close attention to byte size discrepancies, precision, signed/unsigned distinctions, truncation, conversion and casting between types, not-a-number calculations, and how your language handles numbers that are too large or too small for its underlying representation.
  • Perform input validation on any numeric input by ensuring that it is within the expected range. Enforce that the input meets both the minimum and maximum requirements for the expected range.
  • Use the appropriate type for the desired action. For example, in C/C++, only use unsigned types for values that could never be negative, such as height, width, or other numbers related to quantity.

More Incorrect Calculation vulnerabilities (CWE-682)

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 Incorrect Calculation vulnerabilities

Spotted an error? Tell us.