dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2022-23030

MEDIUM · 5.3 CVSS v3.1 Published 2022-01-25
Fix available
A fix is available. Upgrade to after 16.1.1 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
On version 16.1.x before 16.1.2, 15.1.x before 15.1.4.1, 14.1.x before 14.1.4.5, and all versions of 13.1.x, when the BIG-IP Virtual Edition (VE) uses the ixlv driver (which is used in SR-IOV mode and requires Intel X710/XL710/XXV710 family of network adapters on the Hypervisor) and TCP Segmentation Offload configuration is enabled, undisclosed requests may cause an increase in CPU resource utilization. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

When BIG-IP Virtual Edition uses the ixlv driver (SR-IOV mode requiring Intel X710/XL710/XXV710 adapters on the hypervisor) with TCP Segmentation Offload enabled, certain undisclosed network requests trigger excessive CPU utilization, potentially causing denial of service.

MitigationUpgrade BIG-IP VE to version 16.1.2 or later, 15.1.4.1 or later, or 14.1.4.5 or later. Alternatively, if operationally feasible, disable TCP Segmentation Offload configuration.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Big Ip Access Policy ManagerApplication
Affected:>= 13.1.0, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.4>= 16.1.0, <= 16.1.1
Big Ip Advanced Firewall ManagerApplication
Affected:>= 13.1.0, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.4>= 16.1.0, <= 16.1.1
Big Ip Advanced Web Application FirewallApplication
Affected:>= 13.1.0, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.4>= 16.1.0, <= 16.1.1
Big Ip AnalyticsApplication
Affected:>= 13.1.0, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.4>= 16.1.0, <= 16.1.1
Big Ip Application Acceleration ManagerApplication
Affected:>= 13.1.0, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.4>= 16.1.0, <= 16.1.1
Big Ip Application Security ManagerApplication
Affected:>= 13.1.0, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.4>= 16.1.0, <= 16.1.1
Big Ip Ddos Hybrid DefenderApplication
Affected:>= 13.1.0, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.4>= 16.1.0, <= 16.1.1
Big Ip Domain Name SystemApplication
Affected:>= 13.1.0, <= 13.1.4>= 14.1.0, <= 14.1.4>= 15.1.0, <= 15.1.4>= 16.1.0, <= 16.1.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm BIG-IP Virtual Edition is in use
    Verify the platform is a virtual edition instance, not hardware. Check system information or run 'tmsh show sys hardware' to identify the platform type.
    Affected if The system is running on hardware appliance rather than Virtual Edition, as the vulnerability applies only to BIG-IP VE with the ixlv driver.
  2. Identify the installed BIG-IP version
    Run 'tmsh show sys version' or check the version via the web UI (System > Software Management > ISO Image). Compare the version number against the affected ranges: 13.1.0-13.1.4, 14.1.0-14.1.4, 15.1.0-15.1.4, or 16.1.0-16.1.1.
    Affected if The installed version falls within any of the listed ranges.
  3. Verify ixlv driver is loaded
    Run 'modinfo ixlv' or check loaded kernel modules via 'lsmod | grep ixlv' to determine if the ixlv driver (SR-IOV virtual function driver for Intel X710/XL710/XXV710 adapters) is loaded on the system.
    Affected if The ixlv driver is not loaded or present on the system.
  4. Confirm TCP Segmentation Offload is enabled
    Check the network interface configuration for TSO (TCP Segmentation Offload) status. Run 'ethtool -k <interface>' or examine the SR-IOV virtual function settings. Look for 'tcp-segmentation-offload' or 'tso' in the output.
    Affected if TCP Segmentation Offload is enabled on network interfaces using the ixlv driver.

The environment is affected only if running BIG-IP Virtual Edition with a vulnerable version, using the ixlv driver with SR-IOV, and with TCP Segmentation Offload enabled on the affected interfaces.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 16.1.1
Interim mitigation

Upgrade BIG-IP VE to version 16.1.2 or later, 15.1.4.1 or later, or 14.1.4.5 or later. Alternatively, if operationally feasible, disable TCP Segmentation Offload configuration.

Recommended fix High confidence

Upgrade to 16.1.2+ (for 16.1.x), 15.1.4.1+ (for 15.1.x), or 14.1.4.5+ (for 14.1.x); 13.1.x has no fix available (EoTS)

  1. 1. Identify the current BIG-IP VE version by running 'tmsh show sys version' or checking the web UI.
  2. 2. Determine if the system uses the ixlv driver (SR-IOV mode) with Intel X710/XL710/XXV710 network adapters by checking the hypervisor configuration.
  3. 3. Verify if TCP Segmentation Offload is enabled on the affected network interfaces.
  4. 4. If running on affected version 16.1.0-16.1.1, upgrade to version 16.1.2 or later.
  5. 5. If running on affected version 15.1.0-15.1.4, upgrade to version 15.1.4.1 or later.
  6. 6. If running on affected version 14.1.0-14.1.4, upgrade to version 14.1.4.5 or later.
  7. 7. If running on any 13.1.x version, note that this branch is End of Technical Support (EoTS) and no fix is available; plan migration to a supported version (14.1.4.5+, 15.1.4.1+, or 16.1.2+).
  8. 8. After upgrade, verify TCP Segmentation Offload configuration meets operational requirements.
Caveat Review release notes for any configuration or compatibility changes between versions; test upgrade in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Big Ip Access Policy Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-23030 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-23030 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data