dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2022-34655

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.0.x before 16.0.1.1, 15.1.x before 15.1.6.1, and 14.1.x before 14.1.5, when an iRule containing the HTTP::payload command is configured on a virtual server, undisclosed traffic can cause 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

A denial-of-service vulnerability in F5 BIG-IP allows undisclosed traffic combined with an iRule using the HTTP::payload command to crash the Traffic Management Microkernel (TMM), causing service disruption.

MitigationUpgrade BIG-IP to version 16.0.1.1, 15.1.6.1, or 14.1.5 or later. Alternatively, identify and remove/disable iRules using HTTP::payload on affected virtual servers as a temporary workaround until patching is possible.

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.5>= 15.1.0, < 15.1.6.1>= 16.0.0, < 16.0.1.1
Big Ip Advanced Firewall ManagerApplication
Affected:>= 14.1.0, < 14.1.5>= 15.1.0, < 15.1.6.1>= 16.0.0, < 16.0.1.1
Big Ip AnalyticsApplication
Affected:>= 14.1.0, < 14.1.5>= 15.1.0, < 15.1.6.1>= 16.0.0, < 16.0.1.1
Big Ip Application Acceleration ManagerApplication
Affected:>= 14.1.0, < 14.1.5>= 15.1.0, < 15.1.6.1>= 16.0.0, < 16.0.1.1
Big Ip Application Security ManagerApplication
Affected:>= 14.1.0, < 14.1.5>= 15.1.0, < 15.1.6.1>= 16.0.0, < 16.0.1.1
Big Ip Domain Name SystemApplication
Affected:>= 14.1.0, < 14.1.5>= 15.1.0, < 15.1.6.1>= 16.0.0, < 16.0.1.1
Big Ip Fraud Protection ServiceApplication
Affected:>= 14.1.0, < 14.1.5>= 15.1.0, < 15.1.6.1>= 16.0.0, < 16.0.1.1
Big Ip Global Traffic ManagerApplication
Affected:>= 14.1.0, < 14.1.5>= 15.1.0, < 15.1.6.1>= 16.0.0, < 16.0.1.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. Identify BIG-IP version
    Run 'tmsh show sys version' or check the GUI under System > Software > Image List to determine the installed BIG-IP version.
    Affected if The version falls within 14.1.0 to 14.1.4, 15.1.0 to 15.1.6.0, or 16.0.0 to 16.0.1.0.
  2. Locate iRules using HTTP::payload
    Use the BIG-IP configuration utility (Local Traffic > iRules) or run 'tmsh list ltm rule' to list all iRules, then search for 'HTTP::payload' within the iRule definitions.
    Affected if Any iRule deployed on the BIG-IP system contains the HTTP::payload command.
  3. Identify virtual servers using affected iRules
    Run 'tmsh list ltm virtual' to see which virtual servers reference the identified iRules, or check via GUI under Local Traffic > Virtual Servers > Virtual Server List > Resources tab.
    Affected if Virtual servers are associated with iRules containing HTTP::payload.
  4. Confirm TMM process status
    Check TMM status via 'tmsh show sys tmm-info' or monitor for TMM crash logs in /var/log/ltm following a potential exploit attempt.
    Affected if TMM crashes occur after receiving undisclosed traffic combined with HTTP::payload iRule processing.

A system is affected if it runs a vulnerable BIG-IP version (14.1.0-14.1.4, 15.1.0-15.1.6.0, or 16.0.0-16.0.1.0) AND has iRules containing the HTTP::payload command deployed on virtual servers processing traffic.

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.0.1.1 or later
Fixed in 14.1.515.1.6.116.0.1.1
Interim mitigation

Upgrade BIG-IP to version 16.0.1.1, 15.1.6.1, or 14.1.5 or later. Alternatively, identify and remove/disable iRules using HTTP::payload on affected virtual servers as a temporary workaround until patching is possible.

Recommended fix High confidence

14.1.5 (or later 14.1.x), 15.1.6.1 (or later 15.1.x), 16.0.1.1 (or later 16.0.x)

  1. 1. Back up the current BIG-IP configuration using the Configuration Utility or tmsh command: 'tmsh save sys config part2. Download the appropriate hotfix or update from the F5 Downloads site at https://my.f5.com/ (requires F5 support account login)3. Upload the ISO image to the BIG-IP system via the Configuration Utility or SCP4. Mount and install the hotfix using the BIG-IP Configuration Utility
Caveat Upgrading between major versions may introduce behavioral changes; test iRule logic thoroughly in a staging environment before production deployment

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
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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