CVE-2020-5922
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 · uneditedIn BIG-IP versions 15.0.0-15.1.0.4, 14.1.0-14.1.2.6, 13.1.0-13.1.3.3, 12.1.0-12.1.5.1, and 11.6.1-11.6.5.2, iControl REST does not implement Cross Site Request Forgery protections for users which make use of Basic Authentication in a web browser.
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 confidenceF5 BIG-IP iControl REST lacks CSRF protection for users authenticating via Basic Authentication in web browsers, allowing attackers to craft malicious requests that trick authenticated administrators into performing unintended administrative actions.
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.2>= 13.1.0, < 13.1.3.4>= 14.1.0, < 14.1.2.7>= 15.0.0, < 15.1.0.5>= 11.6.1, <= 11.6.5>= 12.1.0, < 12.1.5.2>= 13.1.0, < 13.1.3.4>= 14.1.0, < 14.1.2.7>= 15.0.0, < 15.1.0.5>= 11.6.1, <= 11.6.5>= 12.1.0, < 12.1.5.2>= 13.1.0, < 13.1.3.4>= 14.1.0, < 14.1.2.7>= 15.0.0, < 15.1.0.5>= 11.6.1, <= 11.6.5>= 12.1.0, < 12.1.5.2>= 13.1.0, < 13.1.3.4>= 14.1.0, < 14.1.2.7>= 15.0.0, < 15.1.0.5>= 11.6.1, <= 11.6.5>= 12.1.0, < 12.1.5.2>= 13.1.0, < 13.1.3.4>= 14.1.0, < 14.1.2.7>= 15.0.0, < 15.1.0.5>= 11.6.1, <= 11.6.5>= 12.1.0, < 12.1.5.2>= 13.1.0, < 13.1.3.4>= 14.1.0, < 14.1.2.7>= 15.0.0, < 15.1.0.5>= 11.6.1, <= 11.6.5>= 12.1.0, < 12.1.5.2>= 13.1.0, < 13.1.3.4>= 14.1.0, < 14.1.2.7>= 15.0.0, < 15.1.0.5>= 11.6.1, <= 11.6.5>= 12.1.0, < 12.1.5.2>= 13.1.0, < 13.1.3.4>= 14.1.0, < 14.1.2.7>= 15.0.0, < 15.1.0.5CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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 the installed BIG-IP versionRun command 'tmsh show sys version' on the BIG-IP command line or check System > Software > Image in the web UIAffected if The version falls within any of these ranges: 11.6.1 to 11.6.5, 12.1.0 to 12.1.5.1, 13.1.0 to 13.1.3.3, 14.1.0 to 14.1.2.6, or 15.0.0 to 15.1.0.4
-
Confirm iControl REST interface is accessibleVerify that the iControl REST API endpoint is exposed by attempting to reach https://<management-ip>/mgmt/shared/authz or checking the BIG-IP configuration for restjavad service statusAffected if The iControl REST interface is enabled and reachable on the management network or externally
-
Check if Basic Authentication is used for web UI accessReview the BIG-IP authentication configuration at System > Users > Authentication or inspect /config/bigip_auth.conf for 'basic' authentication methodsAffected if Administrators authenticate to the BIG-IP web interface using Basic Authentication rather than form-based or certificate authentication
The environment is affected if the BIG-IP version is within the vulnerable ranges AND iControl REST is accessible AND administrators use Basic Authentication for browser-based access.
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 data12.1.5.213.1.3.414.1.2.7
Apply the vendor-provided patches for affected BIG-IP versions (15.1.0.5+, 14.1.2.7+, 13.1.3.4+, 12.1.5.2+, 11.6.5.3+) to implement proper CSRF token validation.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-5922 — 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-2020-5922 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