dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2021-22975

HIGH · 7.5 CVSS v3.1 Published 2021-02-12
Fix available
A fix is available. Upgrade to 14.1.3.1 / 15.1.2.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 version 16.0.x before 16.0.1.1, 15.1.x before 15.1.2.1, and 14.1.x before 14.1.3.1, under some circumstances, Traffic Management Microkernel (TMM) may restart on the BIG-IP system while passing large bursts of traffic. Note: Software versions which have reached End of Software Development (EoSD) 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 Traffic Management Microkernel (TMM) allows remote attackers to cause TMM restart by sending large bursts of traffic. The vulnerability affects versions 16.0.x before 16.0.1.1, 15.1.x before 15.1.2.1, and 14.1.x before 14.1.3.1.

MitigationUpgrade BIG-IP to version 16.0.1.1, 15.1.2.1, or 14.1.3.1 or later to remediate this vulnerability.

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.3.1>= 15.1.0, < 15.1.2.1>= 16.0.0, < 16.0.1.1
Big Ip Advanced Firewall ManagerApplication
Affected:>= 14.1.0, < 14.1.3.1>= 15.1.0, < 15.1.2.1>= 16.0.0, < 16.0.1.1
Big Ip Advanced Web Application FirewallApplication
Affected:>= 14.1.0, < 14.1.3.1>= 15.1.0, < 15.1.2.1>= 16.0.0, < 16.0.1.1
Big Ip AnalyticsApplication
Affected:>= 14.1.0, < 14.1.3.1>= 15.1.0, < 15.1.2.1>= 16.0.0, < 16.0.1.1
Big Ip Application Acceleration ManagerApplication
Affected:>= 14.1.0, < 14.1.3.1>= 15.1.0, < 15.1.2.1>= 16.0.0, < 16.0.1.1
Big Ip Application Security ManagerApplication
Affected:>= 14.1.0, < 14.1.3.1>= 15.1.0, < 15.1.2.1>= 16.0.0, < 16.0.1.1
Big Ip Ddos Hybrid DefenderApplication
Affected:>= 14.1.0, < 14.1.3.1>= 15.1.0, < 15.1.2.1>= 16.0.0, < 16.0.1.1
Big Ip Domain Name SystemApplication
Affected:>= 14.1.0, < 14.1.3.1>= 15.1.0, < 15.1.2.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 the BIG-IP device version
    Run `tmsh show /sys version` on the command line or check the GUI under System > Software Information > Version
    Affected if The displayed version is 14.1.x before 14.1.3.1, 15.1.x before 15.1.2.1, or 16.0.x before 16.0.1.1
  2. Confirm the installed modules
    Run `tmsh list /sys module` to list all installed BIG-IP modules
    Affected if Any of these modules are present: Access Policy Manager, Advanced Firewall Manager, Advanced Web Application Firewall, Analytics, Application Acceleration Manager, Application Security Manager, Ddos Hybrid Defender, or Domain Name System
  3. Verify TMM is exposed to network traffic
    Check if TMM virtual servers or self IPs are reachable externally using `tmsh list /ltm virtual` and reviewing network exposure
    Affected if TMM processing is accessible from untrusted networks (external virtual servers, self IPs on external VLANs)

The environment is affected if the BIG-IP version is 14.1.0-14.1.3.0, 15.1.0-15.1.2.0, or 16.0.0-16.0.1.0, any of the listed modules are installed, and TMM is network-accessible.

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.

From vendor data
Upgrade available Upgrade to 14.1.3.1 / 15.1.2.1 / 16.0.1.1 or later
Fixed in 14.1.3.115.1.2.116.0.1.1
Interim mitigation

Upgrade BIG-IP to version 16.0.1.1, 15.1.2.1, or 14.1.3.1 or later to remediate this vulnerability.

Fix this in Big Ip Access Policy Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
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,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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