Big Iq Centralized ManagementApplication · F5
CVE-2020-5868
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-IQ 6.0.0-7.0.0, a remote access vulnerability has been discovered that may allow a remote user to execute shell commands on affected systems using HTTP requests to the BIG-IQ user interface.
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 confidenceA remote command injection vulnerability in F5 BIG-IQ versions 6.0.0-7.0.0 allows unauthenticated remote attackers to execute arbitrary shell commands on affected systems via specially crafted HTTP requests to the web 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
Big Iq Centralized ManagementApplication
>= 6.0.0, <= 6.1.0= 7.0.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 if the system is F5 BIG-IQRun 'tmsh show sys version' or check the system product name via the web interface login page. This vulnerability affects BIG-IQ specifically, not other F5 products like BIG-IP.Affected if The system is F5 BIG-IQ Centralized Management
-
Check the installed BIG-IQ versionLog into the BIG-IQ web interface and navigate to the System > Software Management > Images page, or run 'tmsh show sys version' via SSH. Compare the version to the affected range: 6.0.0-6.1.0 or 7.0.0.Affected if The installed version is 6.0.0, 6.1.0, or 7.0.0
-
Verify the web interface is network-accessibleAttempt to reach the BIG-IQ web interface from an external network or use 'tmsh list sys httpd' to check the listening configuration. Confirm port 443 or 8080 is bound to a reachable interface.Affected if The web interface is exposed on a network interface accessible to untrusted users
-
Check for IP restriction on the management interfaceReview the BIG-IQ Access Policy or firewall rules via 'tmsh list sys httpd allow' and check if iptables or network ACLs are configured to restrict management access to specific IPs.Affected if No IP allow-listing or firewall rules restrict access to the management interface
You are affected if you are running F5 BIG-IQ versions 6.0.0-6.1.0 or 7.0.0 with the web interface accessible to untrusted networks without IP restrictions.
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 dataApply the vendor-supplied patch or upgrade BIG-IQ to a supported version. Until patched, restrict network access to the management interface using firewall rules or IP allow-listing.
Fix this in Big Iq Centralized Management
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-5868 — 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-5868 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