dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2022-23012

HIGH · 7.5 CVSS v3.1 Published 2022-01-25
Fix available
A fix is available. Upgrade to 14.1.4.5 / 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 15.1.x before 15.1.4.1 and 14.1.x before 14.1.4.5, when the HTTP/2 profile is 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 · high confidence

F5 BIG-IP versions 15.1.x before 15.1.4.1 and 14.1.x before 14.1.4.5 contain a denial-of-service vulnerability in the Traffic Management Microkernel (TMM). When an HTTP/2 profile is attached to a virtual server, specially crafted undisclosed requests can cause TMM to terminate, resulting in service disruption for all traffic handled by that virtual server.

MitigationUpgrade BIG-IP to version 15.1.4.1 or 14.1.4.5 or later. As an interim measure, remove or disable the HTTP/2 profile from 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:>= 14.1.0, < 14.1.4.5>= 15.1.0, < 15.1.4.1
Big Ip Advanced Firewall ManagerApplication
Affected:>= 14.1.0, < 14.1.4.5>= 15.1.0, < 15.1.4.1
Big Ip AnalyticsApplication
Affected:>= 14.1.0, < 14.1.4.5>= 15.1.0, < 15.1.4.1
Big Ip Application Acceleration ManagerApplication
Affected:>= 14.1.0, < 14.1.4.5>= 15.1.0, < 15.1.4.1
Big Ip Application Security ManagerApplication
Affected:>= 14.1.0, < 14.1.4.5>= 15.1.0, < 15.1.4.1
Big Ip Domain Name SystemApplication
Affected:>= 14.1.0, < 14.1.4.5>= 15.1.0, < 15.1.4.1
Big Ip Fraud Protection ServiceApplication
Affected:>= 14.1.0, < 14.1.4.5>= 15.1.0, < 15.1.4.1
Big Ip Global Traffic ManagerApplication
Affected:>= 14.1.0, < 14.1.4.5>= 15.1.0, < 15.1.4.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
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. Verify BIG-IP software version
    Run 'tmsh show sys version' or check the BIG-IP login page/version banner to identify the installed version.
    Affected if The version is 14.1.x before 14.1.4.5, or 15.1.x before 15.1.4.1.
  2. Identify HTTP/2 profiles in use
    Run 'tmsh list ltm profile http2' to list all HTTP/2 profiles configured on the system.
    Affected if Any HTTP/2 profiles exist on the system.
  3. Check HTTP/2 profile attachment to virtual servers
    Run 'tmsh list ltm virtual all' and examine the 'profile' or 'profiles' section of each virtual server to see if an HTTP/2 profile is referenced.
    Affected if A virtual server has an HTTP/2 profile assigned to it.

The system is affected if it runs a vulnerable BIG-IP version (14.1.x before 14.1.4.5 or 15.1.x before 15.1.4.1) AND has an HTTP/2 profile attached to any virtual server.

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.5 / 15.1.4.1 or later
Fixed in 14.1.4.515.1.4.1
Interim mitigation

Upgrade BIG-IP to version 15.1.4.1 or 14.1.4.5 or later. As an interim measure, remove or disable the HTTP/2 profile from affected virtual servers until patching can be completed.

Recommended fix High confidence

Upgrade to BIG-IP 14.1.4.5 or later, or 15.1.4.1 or later (or the latest 14.1.x/15.1.x release within those branches)

  1. 1. Identify the current BIG-IP version by running 'tmsh show sys version' or checking the web UI.
  2. 2. Identify all virtual servers that have an HTTP/2 profile configured by reviewing the virtual server configuration or running 'tmsh list ltm virtual one-line | grep http2'.
  3. 3. Create a backup of the BIG-IP configuration using 'tmsh save sys config' or via the web UI.
  4. 4. Schedule a maintenance window as the upgrade will require a brief service interruption.
  5. 5. Download the appropriate hotfix or upgrade image (14.1.4.5 or later for 14.1.x, 15.1.4.1 or later for 15.1.x) from the F5 downloads portal.
  6. 6. Upload the ISO image to the BIG-IP and initiate the upgrade via 'tmsh install sys software' or through the web UI.
  7. 7. After the upgrade completes, verify the new version is running with 'tmsh show sys version'.
  8. 8. Confirm that affected virtual servers with HTTP/2 profiles are functioning correctly and accepting traffic.
Caveat Review F5 release notes for any configuration or compatibility notes when upgrading between versions; test 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
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
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,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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