dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2022-23010

HIGH · 7.5 CVSS v3.1 Published 2022-01-25
Fix available
A fix is available. Upgrade to 14.1.4.4 / 15.1.4.1 or later.
See remediation →
84/100
Remediation priority · High
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 BIG-IP versions 16.x before 16.1.0, 15.1.x before 15.1.4.1, 14.1.x before 14.1.4.4, and all versions of 13.1.x, 12.1.x, and 11.6.x, when a FastL4 profile and an HTTP profile are configured on a virtual server, undisclosed requests can cause an increase in memory 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

This is a memory exhaustion vulnerability in F5 BIG-IP where the combination of FastL4 and HTTP profiles on a virtual server allows undisclosed requests to cause excessive memory utilization, potentially leading to denial of service.

MitigationUpgrade BIG-IP to version 16.1.0, 15.1.4.1, or 14.1.4.4 or later; alternatively, remove either the FastL4 or HTTP profile from affected virtual servers until patching is possible.

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:>= 11.6.0, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, <= 13.1.4>= 14.1.0, < 14.1.4.4>= 15.1.0, < 15.1.4.1>= 16.0.0, < 16.1.0
Big Ip Advanced Firewall ManagerApplication
Affected:>= 11.6.0, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, <= 13.1.4>= 14.1.0, < 14.1.4.4>= 15.1.0, < 15.1.4.1>= 16.0.0, < 16.1.0
Big Ip AnalyticsApplication
Affected:>= 11.6.0, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, <= 13.1.4>= 14.1.0, < 14.1.4.4>= 15.1.0, < 15.1.4.1>= 16.0.0, < 16.1.0
Big Ip Application Acceleration ManagerApplication
Affected:>= 11.6.0, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, <= 13.1.4>= 14.1.0, < 14.1.4.4>= 15.1.0, < 15.1.4.1>= 16.0.0, < 16.1.0
Big Ip Application Security ManagerApplication
Affected:>= 11.6.0, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, <= 13.1.4>= 14.1.0, < 14.1.4.4>= 15.1.0, < 15.1.4.1>= 16.0.0, < 16.1.0
Big Ip Domain Name SystemApplication
Affected:>= 11.6.0, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, <= 13.1.4>= 14.1.0, < 14.1.4.4>= 15.1.0, < 15.1.4.1>= 16.0.0, < 16.1.0
Big Ip Fraud Protection ServiceApplication
Affected:>= 11.6.0, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, <= 13.1.4>= 14.1.0, < 14.1.4.4>= 15.1.0, < 15.1.4.1>= 16.0.0, < 16.1.0
Big Ip Global Traffic ManagerApplication
Affected:>= 11.6.0, <= 11.6.5>= 12.1.0, <= 12.1.6>= 13.1.0, <= 13.1.4>= 14.1.0, < 14.1.4.4>= 15.1.0, < 15.1.4.1>= 16.0.0, < 16.1.0

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
High

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

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. Identify the BIG-IP version
    Run 'tmsh show sys version' or check the web UI under System > Software Management > Image List to find the installed version
    Affected if The installed version falls within: 11.6.0-11.6.5, 12.1.0-12.1.6, 13.1.0-13.1.4, 14.1.0-14.1.4.3, 15.1.0-15.1.4.0, or 16.0.0-16.0.x (before 16.1.0)
  2. List all virtual servers with FastL4 profiles
    Run 'tmsh list ltm virtual profiles' and look for entries where the profile type includes 'ltm profile fastl4', or use the web UI to examine each virtual server's FastL4 profile configuration
    Affected if Any virtual server has a FastL4 profile attached
  3. Identify virtual servers with HTTP profiles
    Run 'tmsh list ltm virtual profiles' and look for entries where the profile type includes 'ltm profile http', or check the web UI for each virtual server's HTTP profile assignment
    Affected if Any virtual server has an HTTP profile attached
  4. Confirm the vulnerable combination exists
    Cross-reference the results from steps 2 and 3 to identify virtual servers that have BOTH a FastL4 profile AND an HTTP profile simultaneously attached
    Affected if A single virtual server has both FastL4 and HTTP profiles configured at the same time

You are affected if your BIG-IP version is within the vulnerable ranges AND you have virtual servers configured with both FastL4 and HTTP profiles together, as this specific profile combination enables the memory exhaustion condition.

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 14.1.4.4 / 15.1.4.1 / 16.1.0 or later
Fixed in 14.1.4.415.1.4.116.1.0
Interim mitigation

Upgrade BIG-IP to version 16.1.0, 15.1.4.1, or 14.1.4.4 or later; alternatively, remove either the FastL4 or HTTP profile from affected virtual servers until patching is possible.

Recommended fix High confidence

14.1.4.4 (or 15.1.4.1 or 16.1.0 or later, depending on target release train)

  1. 1. Identify all BIG-IP devices running affected versions (11.6.x, 12.1.x, 13.1.x, or 14.1.x < 14.1.4.4) with FastL4 and HTTP profiles configured on virtual servers.
  2. 2. Review the current virtual server configurations to confirm FastL4 and HTTP profiles are both in use.
  3. 3. Schedule a maintenance window for the upgrade process.
  4. 4. Backup the current BIG-IP configuration before proceeding with the upgrade.
  5. 5. Upgrade to the appropriate fixed version: 14.1.4.4 or later, 15.1.4.1 or later, or 16.1.0 or later. Note: 11.6.x, 12.1.x, and 13.1.x versions require upgrade to a newer major version as they have reached End of Technical Support and have no patch available.
  6. 6. After upgrade, verify virtual servers are functioning correctly and memory utilization has returned to normal levels.
Caveat Upgrading across major version trains (e.g., 13.1.x to 14.x or higher) may introduce configuration or compatibility changes; review release notes for breaking changes before upgrading. Versions 11.6.x, 12.1.x, and 13.1.x require moving to a newer major version as they are no longer supported.

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 / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-23010 — 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-23010 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