CVE-2021-22989
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 · uneditedOn BIG-IP versions 16.0.x before 16.0.1.1, 15.1.x before 15.1.2.1, 14.1.x before 14.1.4, 13.1.x before 13.1.3.6, 12.1.x before 12.1.5.3, and 11.6.x before 11.6.5.3, when running in Appliance mode with Advanced WAF or BIG-IP ASM provisioned, the TMUI, also referred to as the Configuration utility, has an authenticated remote command execution vulnerability in undisclosed pages. 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 confidenceAuthenticated remote command execution vulnerability in F5 BIG-IP TMUI (Configuration utility) affecting versions 16.0.x before 16.0.1.1, 15.1.x before 15.1.2.1, 14.1.x before 14.1.4, 13.1.x before 13.1.3.6, 12.1.x before 12.1.5.3, and 11.6.x before 11.6.5.3 when running in Appliance mode with Advanced WAF or BIG-IP ASM provisioned. The vulnerability exists in undisclosed pages of the web-based management interface.
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>= 11.6.1, < 11.6.5.3>= 12.1.0, < 12.1.5.3>= 13.1.0, < 13.1.3.6>= 14.1.0, < 14.1.4>= 15.1.0, < 15.1.2.1>= 16.0.0, < 16.0.1.1>= 11.6.1, < 11.6.5.3>= 12.1.0, < 12.1.5.3>= 13.1.0, < 13.1.3.6>= 14.1.0, < 14.1.4>= 15.1.0, < 15.1.2.1>= 16.0.0, < 16.0.1.1>= 11.6.1, < 11.6.5.3>= 12.1.0, < 12.1.5.3>= 13.1.0, < 13.1.3.6>= 14.1.0, < 14.1.4>= 15.1.0, < 15.1.2.1>= 16.0.0, < 16.0.1.1>= 11.6.1, < 11.6.5.3>= 12.1.0, < 12.1.5.3>= 13.1.0, < 13.1.3.6>= 14.1.0, < 14.1.4>= 15.1.0, < 15.1.2.1>= 16.0.0, < 16.0.1.1>= 11.6.1, < 11.6.5.3>= 12.1.0, < 12.1.5.3>= 13.1.0, < 13.1.3.6>= 14.1.0, < 14.1.4>= 15.1.0, < 15.1.2.1>= 16.0.0, < 16.0.1.1>= 11.6.1, < 11.6.5.3>= 12.1.0, < 12.1.5.3>= 13.1.0, < 13.1.3.6>= 14.1.0, < 14.1.4>= 15.1.0, < 15.1.2.1>= 16.0.0, < 16.0.1.1>= 11.6.1, < 11.6.5.3>= 12.1.0, < 12.1.5.3>= 13.1.0, < 13.1.3.6>= 14.1.0, < 14.1.4>= 15.1.0, < 15.1.2.1>= 16.0.0, < 16.0.1.1>= 11.6.1, < 11.6.5.3>= 12.1.0, < 12.1.5.3>= 13.1.0, < 13.1.3.6>= 14.1.0, < 14.1.4>= 15.1.0, < 15.1.2.1>= 16.0.0, < 16.0.1.1CVSS 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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Check BIG-IP version via TMSHRun command: tmsh show /sys version. Look for the version string in the output.Affected if The version is 11.6.x before 11.6.5.3, 12.1.x before 12.1.5.3, 13.1.x before 13.1.3.6, 14.1.x before 14.1.4, 15.1.x before 15.1.2.1, or 16.0.x before 16.0.1.1
-
Verify ASM or Advanced WAF provisioningRun command: tmsh list /sys provision. Look for 'asm' or 'awaf' modules with a level other than 'none'.Affected if ASM (Application Security Manager) or AWAF (Advanced Web Application Firewall) is provisioned on the system
-
Check if Appliance mode is enabledRun command: tmsh list /sys db ui.appliance mode. Alternatively, check System > Repository > Appliance in TMUI or review /config/bigip.conf for 'ui.appliance mode' setting.Affected if The system has Appliance mode enabled (ui.appliance mode is set to 'true')
All three conditions must be true: the BIG-IP version is vulnerable, ASM or AWAF is provisioned, and Appliance mode is enabled. If any one is false, the system is not affected by this specific CVE.
Generated from the published advisory. Verify against your own configuration.
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 · scoped11.6.5.312.1.5.313.1.3.6
Apply F5 hotfixes or upgrade to the fixed versions (16.0.1.1, 15.1.2.1, 14.1.4, 13.1.3.6, 12.1.5.3, 11.6.5.3). Until patched, restrict TMUI access to trusted management networks only and enforce strong authentication.
Upgrade to 11.6.5.3+ (11.6.x), 12.1.5.3+ (12.1.x), 13.1.3.6+ (13.1.x), or 14.1.4+ (14.1.x) depending on your current branch
- 1. Identify the current installed BIG-IP version by running 'tmsh show sys version' or checking the TMUI version information.
- 2. Based on the current version branch, upgrade to the minimum fixed version: for 11.6.x upgrade to 11.6.5.3 or later; for 12.1.x upgrade to 12.1.5.3 or later; for 13.1.x upgrade to 13.1.3.6 or later; for 14.1.x upgrade to 14.1.4 or later.
- 3. Download the appropriate hotfix or ISO image from the F5 Networks downloads portal at support.f5.com.
- 4. Review F5 upgrade documentation and ensure proper backups are in place before proceeding.
- 5. Upload the ISO or hotfix to the BIG-IP system and install using 'tmsh install sys software' or via the TMUI.
- 6. After installation, reboot the system to apply the changes.
- 7. Verify the version has been updated by running 'tmsh show sys version' and confirm the vulnerability is resolved.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22989 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-22989 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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