Big Iq Centralized ManagementApplication · F5
CVE-2019-6653
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 · uneditedThere is a Stored Cross Site Scripting vulnerability in the undisclosed page of a BIG-IQ 6.0.0-6.1.0 or 5.2.0-5.4.0 system. The attack can be stored by users granted the Device Manager and Administrator roles.
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 confidenceStored Cross Site Scripting (XSS) vulnerability in an undisclosed page of F5 BIG-IQ management interface versions 6.0.0-6.1.0 and 5.2.0-5.4.0. Attackers with Device Manager or Administrator role privileges can inject malicious JavaScript that persists on the affected page, executing in browsers of other users viewing that content.
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
>= 5.2.0, <= 5.4.0>= 6.0.0, <= 6.1.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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed BIG-IQ versionLog into the BIG-IQ management interface and navigate to System > Software Management > Images, or run 'tmsh show sys version' via command line to retrieve the exact version numberAffected if The installed version falls within 5.2.0 through 5.4.0, or 6.0.0 through 6.1.0
-
Confirm BIG-IQ management interface is accessibleVerify that the web-based management interface (typically port 443 or 8443) is reachable on the networkAffected if The management interface is exposed and reachable
-
Review user accounts with elevated rolesNavigate to System > Users > User List or use 'tmsh list auth user' command to enumerate all user accounts and their assigned rolesAffected if Any user account possesses Device Manager or Administrator role privileges
-
Check for suspicious user activity or injected contentReview audit logs under System > Logs > Audit for entries indicating unexpected script injection or unusual content in page submissionsAffected if Audit logs show anomalous script tags or JavaScript patterns in form submissions
The environment is affected if the installed BIG-IQ version is 5.2.0-5.4.0 or 6.0.0-6.1.0 and the management interface is accessible to users with Device Manager or Administrator roles, as the vulnerability requires these privileges to inject the stored XSS payload.
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 F5 vendor patches when available. Restrict administrative access to trusted personnel only and monitor for suspicious activity in the interim.
Fix this in Big Iq Centralized Management
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6653 — 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-2019-6653 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