Big Iq Centralized ManagementApplication · F5

CVE-2021-23006

MEDIUM · 6.1 CVSS v3.1 Published 2021-03-31
Fix available
A fix is available. Upgrade to 8.0.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
On all 7.x and 6.x versions (fixed in 8.0.0), undisclosed BIG-IQ pages have a reflected cross-site scripting vulnerability. 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 · moderate confidence

Reflected cross-site scripting (XSS) vulnerability in undisclosed BIG-IQ management interface pages. The vulnerability allows attackers to inject malicious scripts through crafted URLs that are reflected back in the server response without proper sanitization.

MitigationUpgrade BIG-IQ to version 8.0.0 or later. Until upgraded, implement input validation and output encoding on web application endpoints, and consider deploying a WAF to filter malicious requests.

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:>= 6.0.0, < 8.0.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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 installed BIG-IQ version
    Access the BIG-IQ management interface and navigate to the System > Software > Image List section, or use the command line and run 'tmsh show sys version' to retrieve the installed software version.
    Affected if The reported version is >= 6.0.0 and < 8.0.0, placing it within the vulnerable range.
  2. Verify management interface accessibility
    Confirm that the BIG-IQ web management interface is accessible from network locations. Check the BIG-IQ network configuration and determine if port 443 or the management IP is exposed to untrusted networks.
    Affected if The management interface is accessible from networks where attackers could craft and send malicious URLs.
  3. Review HTTP access logs for anomalous URL patterns
    Examine BIG-IQ HTTP access logs (typically found in /var/log/httptraffic/ or via the Logs > HTTP Requests section in the GUI) for any unusual query parameters, especially those containing script tags, javascript:, or HTML tags that may indicate XSS probe attempts.
    Affected if Suspicious URL patterns with XSS payloads are found in the logs, suggesting potential exploitation attempts.
  4. Check for unexpected or unauthorized user sessions
    Review the BIG-IQ logs for any unexpected authenticated sessions, particularly from users who should not have access or from IP addresses that are not recognized. Look in System > Logs > Audit for authentication events.
    Affected if Audit logs show unauthorized access or session anomalies that could indicate successful XSS exploitation leading to session hijacking.

A user is affected if their BIG-IQ version is between 6.0.0 and 8.0.0 and the management interface is network-accessible to potential attackers who could inject malicious scripts through crafted URLs.

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 8.0.0 or later
Fixed in 8.0.0
Interim mitigation

Upgrade BIG-IQ to version 8.0.0 or later. Until upgraded, implement input validation and output encoding on web application endpoints, and consider deploying a WAF to filter malicious requests.

Fix this in Big Iq Centralized Management Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-23006 — 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-2021-23006 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