dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2023-22422

HIGH · 7.5 CVSS v3.1 Developing 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, when a HTTP profile with the non-default Enforcement options of Enforce HTTP Compliance and Unknown Methods: Reject are configured on a virtual server, 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.

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 · low confidence
Developing — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-08-01.

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

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
Recommended fix High confidence

BIG‑IP 16.1.3.3 or 17.0.0.2 (or later)

  1. Identify the currently installed BIG‑IP version (e.g., run `tmsh show sys version` or `bigpipe version`).
  2. Determine whether the version falls within the affected range: 16.1.x before 16.1.3.3 or 17.0.x before 17.0.0.2.
  3. Schedule a maintenance window for the upgrade.
  4. As a temporary mitigation, locate any HTTP profile that has both “Enforce HTTP Compliance” and “Unknown Methods: Reject” enabled and either disable those options or replace the profile with a compliant one.
  5. Obtain the fixed BIG‑IP software image (16.1.3.3 or 17.0.0.2 or later) from the F5 downloads portal and upload it to the BIG‑IP (e.g., to /var/lib/ucs).
  6. Install the upgrade following F5’s standard upgrade procedure (e.g., `tmsh install sys software` or the GUI software upgrade page) and reboot the device.
  7. After the system restarts, verify the new version (e.g., `tmsh show sys version`) and confirm that the HTTP profile still functions as expected.
  8. Monitor the system and review the release notes for any additional changes or known issues.
Caveat Review the release notes for the target version; upgrades may introduce behavior changes or require downtime.

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $3,200. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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