dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2022-32455

HIGH · 7.5 CVSS v3.1 Published 2022-08-04
Fix available
A fix is available. Upgrade to 14.1.5 / 15.1.6.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
In BIG-IP Versions 16.1.x before 16.1.2.2, 15.1.x before 15.1.6.1, 14.1.x before 14.1.5, and all versions of 13.1.x, when a BIG-IP LTM Client SSL profile is configured on a virtual server to perform client certificate authentication with session tickets enabled, undisclosed requests 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 · moderate confidence

A denial-of-service vulnerability exists in BIG-IP LTM where specially crafted requests to virtual servers configured with a Client SSL profile that has both client certificate authentication and session tickets enabled cause the Traffic Management Microkernel (TMM) to terminate. The exact request format is undisclosed.

MitigationUpgrade BIG-IP to version 16.1.2.2 or later (16.1.x), 15.1.6.1 or later (15.1.x), 14.1.5 or later (14.1.x), or 13.1.x to the latest supported version. As a temporary workaround, if business requirements permit, consider disabling client certificate authentication or session tickets in affected Client SSL profiles 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:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5>= 15.1.0, < 15.1.6.1>= 16.1.0, < 16.1.2.2
Big Ip Advanced Firewall ManagerApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5>= 15.1.0, < 15.1.6.1>= 16.1.0, < 16.1.2.2
Big Ip AnalyticsApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5>= 15.1.0, < 15.1.6.1>= 16.1.0, < 16.1.2.2
Big Ip Application Acceleration ManagerApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5>= 15.1.0, < 15.1.6.1>= 16.1.0, < 16.1.2.2
Big Ip Application Security ManagerApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5>= 15.1.0, < 15.1.6.1>= 16.1.0, < 16.1.2.2
Big Ip Domain Name SystemApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5>= 15.1.0, < 15.1.6.1>= 16.1.0, < 16.1.2.2
Big Ip Fraud Protection ServiceApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5>= 15.1.0, < 15.1.6.1>= 16.1.0, < 16.1.2.2
Big Ip Global Traffic ManagerApplication
Affected:>= 13.1.0, <= 13.1.5>= 14.1.0, < 14.1.5>= 15.1.0, < 15.1.6.1>= 16.1.0, < 16.1.2.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 version
    Run `tmsh show sys version` or view the version in the GUI under Dashboard. Confirm the exact version number.
    Affected if Version falls within 13.1.0-13.1.5, 14.1.0-14.1.4, 15.1.0-15.1.6.0, or 16.1.0-16.1.2.1
  2. Identify Client SSL profiles
    Run `tmsh list /ltm profile client-ssl all` to list all Client SSL profiles configured on the system.
    Affected if Any Client SSL profiles exist on the system
  3. Check client certificate authentication setting
    For each Client SSL profile, run `tmsh list /ltm profile client-ssl <profile_name>` and examine the 'cert' field under 'client-auth'. Values of 'request' or 'require' indicate client certificate authentication is enabled.
    Affected if Any Client SSL profile has client certificate authentication set to 'request' or 'require'
  4. Check session tickets setting
    For each Client SSL profile, run `tmsh list /ltm profile client-ssl <profile_name>` and examine the 'session-ticket' field. A value of 'enabled' indicates session tickets are active.
    Affected if Any Client SSL profile has session tickets enabled

Environment is affected if the BIG-IP version is within the vulnerable ranges AND at least one virtual server uses a Client SSL profile that has BOTH client certificate authentication (request/require) and session tickets enabled.

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.5 / 15.1.6.1 / 16.1.2.2 or later
Fixed in 14.1.515.1.6.116.1.2.2
Interim mitigation

Upgrade BIG-IP to version 16.1.2.2 or later (16.1.x), 15.1.6.1 or later (15.1.x), 14.1.5 or later (14.1.x), or 13.1.x to the latest supported version. As a temporary workaround, if business requirements permit, consider disabling client certificate authentication or session tickets in affected Client SSL profiles until patching can be completed.

Recommended fix High confidence

BIG-IP 14.1.5+, 15.1.6.1+, or 16.1.2.2+ (13.1.x has no fix - EoTS)

  1. 1. Identify affected BIG-IP devices by checking the currently installed version (System > Software Management > Image List in the BIG-IP Configuration Utility).
  2. 2. Verify if the device has a Client SSL profile configured with client certificate authentication and session tickets enabled (Local Traffic > Profiles > SSL > Client).
  3. 3. For BIG-IP 13.1.x: Note that all versions are End of Technical Support (EoTS) and no patch is available; consider upgrading to a supported version (14.1.5+, 15.1.6.1+, or 16.1.2.2+).
  4. 4. For BIG-IP 14.1.x: Upgrade to version 14.1.5 or later.
  5. 5. For BIG-IP 15.1.x: Upgrade to version 15.1.6.1 or later.
  6. 6. For BIG-IP 16.1.x: Upgrade to version 16.1.2.2 or later.
  7. 7. After upgrade, verify the TMM process is running properly (tmsh show sys tmm-info).
Caveat Upgrading BIG-IP may require thorough testing of existing configurations, especially SSL profiles and client certificate authentication flows; also review release notes for any known issues in target version.

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
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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