Big Iq Centralized ManagementApplication · F5

CVE-2020-5870

HIGH · 8.1 CVSS v3.1 Published 2020-04-24
Fix available
A fix is available. Upgrade to 7.1.0 or later.
See remediation →
86/100
Remediation priority · High
No privileges Zero-click

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 · unedited
In BIG-IQ 5.2.0-7.0.0, high availability (HA) synchronization mechanisms do not use any form of authentication for connecting to the peer.

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 confidence

In BIG-IQ versions 5.2.0 through 7.0.0, the High Availability (HA) synchronization mechanism lacks authentication, allowing any device on the network to establish a sync connection to the peer without credentials. This unauthenticated access could enable an attacker to intercept or manipulate HA synchronization data.

MitigationUpgrade BIG-IQ to version 7.0.1 or later. If immediate upgrade is not possible, restrict network access to HA sync ports (port 4353) using firewall rules or VLAN segmentation to prevent unauthorized peers from reaching the HA 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
Affected:>= 5.2.0, <= 5.4.0>= 6.0.0, <= 6.1.0>= 7.0.0, < 7.1.0

CVSS 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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed BIG-IQ version
    Run the command 'tmsh show sys version' on the BIG-IQ device or check the version displayed in the BIG-IQ web interface under the System > Software Management section
    Affected if The installed version falls within these ranges: 5.2.0-5.4.0, 6.0.0-6.1.0, or 7.0.0-7.0.x (versions below 7.1.0)
  2. Verify if High Availability synchronization is enabled
    In the BIG-IQ web interface, navigate to Device Management > Devices and check if the device is configured as part of an HA pair. Alternatively, run 'tmsh show cm device-group' to list device groups and identify sync-only or sync-failover groups
    Affected if The device is a member of a sync device-group with HA synchronization enabled
  3. Confirm network exposure of HA sync port 4353
    Run 'tmsh show net listen' or 'ss -ln | grep 4353' to verify the HA sync port is listening. Then check firewall rules with 'tmsh list net firewall rule all' or review network access lists to determine if port 4353 is accessible from untrusted networks
    Affected if Port 4353 is listening and accessible from network segments that include untrusted or non-HA devices
  4. Review HA peer configuration for unexpected devices
    Run 'tmsh list cm device-group <group-name>' to view the peer devices configured in the HA group. Verify that only expected, authorized peer IP addresses are listed
    Affected if The HA device-group contains unexpected peer IP addresses or shows connections from unknown devices

You are affected if BIG-IQ version is below 7.1.0, HA synchronization is enabled, and port 4353 is accessible from untrusted network segments.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 7.1.0 or later
Fixed in 7.1.0
Interim mitigation

Upgrade BIG-IQ to version 7.0.1 or later. If immediate upgrade is not possible, restrict network access to HA sync ports (port 4353) using firewall rules or VLAN segmentation to prevent unauthorized peers from reaching the HA interface.

Fix this in Big Iq Centralized Management Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-5870 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-5870 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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