CVE-2020-5930
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 15.0.0-15.1.0.4, 14.1.0-14.1.2.7, 13.1.0-13.1.3.3, 12.1.0-12.1.5.2, and 11.6.1-11.6.5.2 and BIG-IQ 5.2.0-7.1.0, unauthenticated attackers can cause disruption of service via undisclosed methods.
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 · moderate confidenceUnauthenticated remote attackers can cause disruption of service on affected F5 BIG-IP and BIG-IQ devices. The vulnerability is rated HIGH (CVSS 7.5) and affects multiple versions across the 11.x, 12.x, 13.x, 14.x, and 15.x product lines, as well as BIG-IQ versions 5.2.0-7.1.0. The specific attack vector and technical details are undisclosed in the advisory.
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.4>= 14.1.0, < 14.1.2.8>= 15.1.0, < 15.1.0.5>= 11.6.1, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.1.0, < 13.1.3.4>= 14.1.0, < 14.1.2.8>= 15.1.0, < 15.1.0.5>= 11.6.1, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.1.0, < 13.1.3.4>= 14.1.0, < 14.1.2.8>= 15.1.0, < 15.1.0.5>= 11.6.1, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.1.0, < 13.1.3.4>= 14.1.0, < 14.1.2.8>= 15.1.0, < 15.1.0.5>= 11.6.1, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.1.0, < 13.1.3.4>= 14.1.0, < 14.1.2.8>= 15.1.0, < 15.1.0.5>= 11.6.1, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.1.0, < 13.1.3.4>= 14.1.0, < 14.1.2.8>= 15.1.0, < 15.1.0.5>= 11.6.1, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.1.0, < 13.1.3.4>= 14.1.0, < 14.1.2.8>= 15.1.0, < 15.1.0.5>= 11.6.1, <= 11.6.5>= 12.1.0, <= 12.1.5>= 13.1.0, < 13.1.3.4>= 14.1.0, < 14.1.2.8>= 15.1.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed BIG-IP versionRun `tmsh show /sys version` or check the web UI under System > Software Management > ISO Image. Alternatively, run `bigpipe version` from the command line.Affected if The version falls within 11.6.1-11.6.5, 12.1.0-12.1.5, 13.1.0-13.1.3.3, 14.1.0-14.1.2.7, or 15.1.0-15.1.0.4.
-
Verify if any affected BIG-IP modules are provisionedRun `tmsh list /sys provision` to list all provisioned modules. Check the 'level' column - any module with a level other than 'none' is provisioned.Affected if Any of these modules are provisioned: APM, AFM, Analytics, AAM, ASM, DNS, Edge Gateway, or Fraud Protection Service, AND the version is in the affected range.
-
Check BIG-IQ version if applicableLog into the BIG-IQ web interface and navigate to the System > Software Management page, or run `tmsh show /sys version` from the CLI.Affected if The BIG-IQ version is between 5.2.0 and 7.1.0 inclusive.
-
Confirm the specific module version (optional)For each provisioned affected module, run `tmsh list /sys software` or check the installed hotfixes via `tmsh show /sys hotfix`.Affected if The module version matches the affected BIG-IP version ranges listed in step 1.
You are affected if your BIG-IP version falls within the vulnerable ranges AND any of the eight affected modules (APM, AFM, Analytics, AAM, ASM, DNS, Edge Gateway, Fraud Protection Service) are provisioned, or if your BIG-IQ version is between 5.2.0 and 7.1.0.
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.414.1.2.815.1.0.5
Apply the vendor-supplied patches/updates to upgrade to a fixed version outside the affected version ranges. For BIG-IP: 15.1.0.5+, 14.1.2.8+, 13.1.3.4+, 12.1.5.3+, 11.6.5.3+. For BIG-IQ: 7.1.0.1+ or later.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-5930 — 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-5930 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