Big Iq Centralized ManagementApplication · F5
CVE-2021-22996
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 all 7.x versions (fixed in 8.0.0), when set up for auto failover, a BIG-IQ Data Collection Device (DCD) cluster member that receives an undisclosed message may cause the corosync process to abort. This behavior may lead to a denial-of-service (DoS) and impact the stability of a BIG-IQ high availability (HA) cluster. 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 confidenceIn F5 BIG-IQ Data Collection Device (DCD) versions 7.x, when configured for auto failover in a high-availability cluster, receiving a specific undisclosed message causes the corosync process to abort. This crash triggers a denial-of-service condition and destabilizes the entire HA cluster, preventing failover functionality.
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
>= 7.0.0, < 8.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
- 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 BIG-IQ DCD versionRun 'tmsh show /sys version' or access the BIG-IQ web UI to view the system version under System > Software Management > ISO ImageAffected if The installed version is 7.x (greater than or equal to 7.0.0 but less than 8.0.0)
-
Confirm the unit is a Data Collection Device (DCD)Access BIG-IQ web UI and navigate to System > Deployment > Overview to verify the device role is configured as a DCDAffected if The device is a BIG-IQ DCD (not a Central Manager or other BIG-IQ variant)
-
Verify high-availability cluster configurationCheck System > High Availability in the BIG-IQ web UI or run 'tmsh show /cm device-group' to confirm the DCD is part of a device groupAffected if The DCD is configured in a cluster with at least one peer device
-
Confirm auto failover is enabledReview the HA cluster settings in System > High Availability to determine if auto failover is toggled onAffected if Auto failover is enabled on the HA cluster configuration
You are affected if your BIG-IQ DCD runs version 7.x and is configured in an HA cluster with auto failover enabled, as this is the specific configuration that triggers the corosync abort condition.
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 data8.0.0
Upgrade BIG-IQ DCD to version 8.0.0 or later. Prior to upgrade, schedule a maintenance window and test failover behavior in a non-production environment.
Fix this in Big Iq Centralized Management
Scoped from the published advisory
- Consultation4.0 h
- Implementation6.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22996 — 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-22996 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