dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2023-22302

MEDIUM · 5.9 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 →
68/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
In BIG-IP versions 17.0.x before 17.0.0.2, and 16.1.x beginning in 16.1.2.2 to before 16.1.3.3, when an HTTP profile is configured on a virtual server and conditions beyond the attacker’s control exist on the target pool member, undisclosed requests sent to the BIG-IP system can cause the Traffic Management Microkernel (TMM) to terminate. 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 · high confidence

In BIG-IP versions 17.0.x before 17.0.0.2 and 16.1.x from 16.1.2.2 to before 16.1.3.3, an attacker can cause the Traffic Management Microkernel (TMM) to terminate by sending undisclosed requests to a virtual server that has an HTTP profile configured, when specific conditions exist on the target pool member.

MitigationUpgrade BIG-IP to version 17.0.0.2 or later, or 16.1.3.3 or later. Until patched, monitor TMM availability and consider restricting pool member access to reduce attack surface.

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.2.2, < 16.1.3.3>= 17.0.0, < 17.0.0.2
Big Ip Advanced Firewall ManagerApplication
Affected:>= 16.1.2.2, < 16.1.3.3>= 17.0.0, < 17.0.0.2
Big Ip AnalyticsApplication
Affected:>= 16.1.2.2, < 16.1.3.3>= 17.0.0, < 17.0.0.2
Big Ip Application Acceleration ManagerApplication
Affected:>= 16.1.2.2, < 16.1.3.3>= 17.0.0, < 17.0.0.2
Big Ip Application Security ManagerApplication
Affected:>= 16.1.2.2, < 16.1.3.3>= 17.0.0, < 17.0.0.2
Big Ip Ddos Hybrid DefenderApplication
Affected:>= 16.1.2.2, < 16.1.3.3>= 17.0.0, < 17.0.0.2
Big Ip Domain Name SystemApplication
Affected:>= 16.1.2.2, < 16.1.3.3>= 17.0.0, < 17.0.0.2
Big Ip Fraud Protection ServiceApplication
Affected:>= 16.1.2.2, < 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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:H/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 version
    Run 'tmsh show sys version' or 'bigpipe version' to retrieve the installed BIG-IP version
    Affected if The version is 16.1.2.2 through 16.1.3.2, or 17.0.0 through 17.0.0.1
  2. Identify virtual servers with HTTP profiles
    Run 'tmsh list ltm virtual one-line' and look for virtual servers that reference an HTTP profile in their 'profile' section
    Affected if A virtual server exists with an HTTP profile (such as http or a custom HTTP profile) configured
  3. Verify TMM process status
    Run 'tmsh show sys tmm-info' or 'bigstart status tmm' to check if the Traffic Management Microkernel is running
    Affected if TMM is running and the version is within the affected range, indicating the vulnerable component is active

You are affected if your BIG-IP version is 16.1.2.2-16.1.3.2 or 17.0.0-17.0.0.1 AND you have a virtual server with an HTTP profile configured pointing to pool members.

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

Upgrade BIG-IP to version 17.0.0.2 or later, or 16.1.3.3 or later. Until patched, monitor TMM availability and consider restricting pool member access to reduce attack surface.

Recommended fix High confidence

Upgrade to BIG-IP 16.1.3.3 or later, or BIG-IP 17.0.0.2 or later

  1. 1. Identify all affected BIG-IP deployments by checking the installed version (tmsh show sys version)
  2. 2. For systems running 16.1.x versions >= 16.1.2.2 and < 16.1.3.3, upgrade to version 16.1.3.3 or later
  3. 3. For systems running 17.0.x versions >= 17.0.0 and < 17.0.0.2, upgrade to version 17.0.0.2 or later
  4. 4. Verify the upgrade was successful by confirming the new version (tmsh show sys version)
  5. 5. Test that virtual servers with HTTP profiles function properly after upgrade
Caveat Review F5 release notes for any known issues or configuration changes required between versions

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
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
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,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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