dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2023-22664

HIGH · 7.5 CVSS v3.1 Published 2023-02-01
Fix available
A fix is available. Upgrade to 16.1.3.3 / 17.0.0.2 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 17.0.x before 17.0.0.2 and 16.1.x before 16.1.3.3, and BIG-IP SPK starting in version 1.6.0, when a client-side HTTP/2 profile and the HTTP MRF Router option are enabled for 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 specific configurations (client-side HTTP/2 profile combined with HTTP MRF Router enabled on a virtual server) allow specially crafted requests to cause excessive memory consumption, potentially leading to denial of service.

MitigationApply F5 BIG-IP software updates 17.0.0.2 or later for 17.x and 16.1.3.3 or later for 16.x. As a temporary workaround, consider disabling either the HTTP/2 profile or the HTTP MRF Router option on affected virtual servers until patching can be completed.

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:>= 16.1.0, < 16.1.3.3>= 17.0.0, < 17.0.0.2
Big Ip Advanced Firewall ManagerApplication
Affected:>= 16.1.0, < 16.1.3.3>= 17.0.0, < 17.0.0.2
Big Ip AnalyticsApplication
Affected:>= 16.1.0, < 16.1.3.3>= 17.0.0, < 17.0.0.2
Big Ip Application Acceleration ManagerApplication
Affected:>= 16.1.0, < 16.1.3.3>= 17.0.0, < 17.0.0.2
Big Ip Application Security ManagerApplication
Affected:>= 16.1.0, < 16.1.3.3>= 17.0.0, < 17.0.0.2
Big Ip Ddos Hybrid DefenderApplication
Affected:>= 16.1.0, < 16.1.3.3>= 17.0.0, < 17.0.0.2
Big Ip Domain Name SystemApplication
Affected:>= 16.1.0, < 16.1.3.3>= 17.0.0, < 17.0.0.2
Big Ip Fraud Protection ServiceApplication
Affected:>= 16.1.0, < 16.1.3.3>= 17.0.0, < 17.0.0.2

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. Check BIG-IP software version
    Run 'tmsh show sys version' or view the System > Software Management > ISO Image page in the management GUI. Note the base version number (e.g., 16.1.x or 17.0.x).
    Affected if Version is 16.1.0 through 16.1.3.2 OR 17.0.0 through 17.0.0.1
  2. Identify virtual servers with client-side HTTP/2 profile enabled
    Run 'tmsh list ltm virtual <virtual_name> http2' to check each virtual server, or use 'tmsh show ltm virtual' and filter for http2 profile references in the output.
    Affected if Any virtual server has a client-side HTTP/2 profile explicitly enabled or assigned
  3. Check if HTTP MRF Router is enabled on virtual servers
    Run 'tmsh list ltm virtual <virtual_name> profile http mrfrouter' for each virtual server, or search for 'mrfrouter' in the virtual server configuration with 'tmsh list ltm virtual all | grep -A 20 mrfrouter'.
    Affected if HTTP MRF Router option is enabled (set to 'enabled' or 'yes') on any virtual server that also has an HTTP/2 profile
  4. Verify combination of both conditions on same virtual server
    Cross-reference the results from steps 2 and 3 to identify virtual servers that have BOTH an HTTP/2 profile AND HTTP MRF Router enabled simultaneously.
    Affected if A single virtual server has both HTTP/2 profile enabled AND HTTP MRF Router enabled

You are affected if your BIG-IP runs version 16.1.0-16.1.3.2 or 17.0.0-17.0.0.1 AND any virtual server has both a client-side HTTP/2 profile and HTTP MRF Router enabled concurrently.

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 16.1.3.3 / 17.0.0.2 or later
Fixed in 16.1.3.317.0.0.2
Interim mitigation

Apply F5 BIG-IP software updates 17.0.0.2 or later for 17.x and 16.1.3.3 or later for 16.x. As a temporary workaround, consider disabling either the HTTP/2 profile or the HTTP MRF Router option on affected virtual servers until patching can be completed.

Recommended fix High confidence

16.1.3.3 or 17.0.0.2 (depending on your current major version branch)

  1. Identify virtual servers with client-side HTTP/2 profile and HTTP MRF Router option enabled that may be vulnerable
  2. Plan upgrade to a fixed version considering your current major version (16.1.x or 17.0.x)
  3. Test the upgrade in a non-production environment first
  4. Schedule a maintenance window for the upgrade
  5. For BIG-IP 16.1.x: Upgrade to version 16.1.3.3 or later
  6. For BIG-IP 17.0.x: Upgrade to version 17.0.0.2 or later
  7. After upgrade, verify that virtual servers with HTTP/2 profile and HTTP MRF Router are functioning correctly
  8. Monitor memory utilization to confirm the vulnerability is remediated

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
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
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,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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