CVE-2021-22978
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 version 16.0.x before 16.0.1, 15.1.x before 15.1.1, 14.1.x before 14.1.3.1, 13.1.x before 13.1.3.5, and all 12.1.x and 11.6.x versions, undisclosed endpoints in iControl REST allow for a reflected XSS attack, which could lead to a complete compromise of BIG-IP if the victim user is granted the admin role. 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 confidenceReflected cross-site scripting (XSS) vulnerability in undisclosed iControl REST API endpoints on F5 BIG-IP. The vulnerability allows attackers to inject malicious scripts through crafted requests that are reflected back to the victim user's browser, enabling session hijacking or arbitrary actions when an administrator unknowingly executes the payload.
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>= 12.1.0, <= 12.1.5>= 13.1.0, < 13.1.3.5>= 14.1.0, < 14.1.3.1>= 15.1.0, < 15.1.1>= 16.0.0, < 16.0.1>= 11.6.1, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.1.0, < 13.1.3.5>= 14.1.0, < 14.1.3.1>= 15.1.0, < 15.1.1>= 16.0.0, < 16.0.1>= 11.6.1, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.1.0, < 13.1.3.5>= 14.1.0, < 14.1.3.1>= 15.1.0, < 15.1.1>= 16.0.0, < 16.0.1>= 11.6.1, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.1.0, < 13.1.3.5>= 14.1.0, < 14.1.3.1>= 15.1.0, < 15.1.1>= 16.0.0, < 16.0.1>= 11.6.1, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.1.0, < 13.1.3.5>= 14.1.0, < 14.1.3.1>= 15.1.0, < 15.1.1>= 16.0.0, < 16.0.1>= 11.6.1, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.1.0, < 13.1.3.5>= 14.1.0, < 14.1.3.1>= 15.1.0, < 15.1.1>= 16.0.0, < 16.0.1>= 11.6.1, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.1.0, < 13.1.3.5>= 14.1.0, < 14.1.3.1>= 15.1.0, < 15.1.1>= 16.0.0, < 16.0.1>= 11.6.1, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.1.0, < 13.1.3.5>= 14.1.0, < 14.1.3.1>= 15.1.0, < 15.1.1>= 16.0.0, < 16.0.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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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.
-
Identify installed BIG-IP versionRun `tmsh show /sys version` on the BIG-IP command line, or query the iControl REST endpoint GET /mgmt/tm/sys/version/ to retrieve the software version.Affected if The installed version falls within these ranges: 11.6.1 to 11.6.5, 12.1.0 to 12.1.5, 13.1.0 to 13.1.3.4, 14.1.0 to 14.1.3.0, 15.1.0 to 15.1.0, or 16.0.0 to 16.0.0.
-
Verify iControl REST is accessibleConfirm that the iControl REST API is exposed by attempting to access the endpoint GET /mgmt/tm/sys/ from a management interface or checking if port 443 (or custom mgmt port) accepts REST API requests.Affected if iControl REST API is reachable from network segments that include untrusted users, particularly the management network.
-
Check which BIG-IP modules are provisionedRun `tmsh list sys provision` or query GET /mgmt/tm/sys/provision/ to list provisioned modules.Affected if Any of the following modules are provisioned: APM, AFM, ASM, Analytics, AAM, DNS, or DDoS Hybrid Defender.
-
Review access logs for suspicious iControl REST requestsExamine /var/log/audit for iControl REST API calls that may contain XSS payloads (look for unusual script tags or encoded characters in API request paths or parameters).
You are affected if your BIG-IP version is within the affected ranges AND iControl REST API is accessible from an untrusted network AND one or more affected modules (APM, AFM, ASM, Analytics, AAM, DNS, DDoS) are provisioned.
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.
From vendor data13.1.3.514.1.3.115.1.1
Apply F5 security updates for affected versions (16.0.1+, 15.1.1+, 14.1.3.1+, 13.1.3.5+). Until patched, restrict iControl REST access to trusted networks only and monitor for anomalous requests.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22978 — 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-22978 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