Big Iq Centralized ManagementApplication · F5
CVE-2019-6652
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-6.1.0, services for stats do not require authentication nor do they implement any form of Transport Layer Security (TLS).
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 BIG-IQ versions 6.0.0 through 6.1.0, the statistics services expose data without requiring any authentication credentials and without encrypting the communication channel via TLS. This allows unauthenticated attackers on the network to intercept or access sensitive statistical data in plaintext.
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.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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 versionAccess the BIG-IQ management interface or run the version command via CLI (e.g., 'tmsh show sys version' or check via the web UI under System > Software Management > Images)Affected if The installed version falls within 6.0.0 through 6.1.0 (inclusive)
-
Locate the statistics service endpointsIdentify running statistics service listeners on the BIG-IQ device (commonly ports such as 8443 or 443 for REST APIs; check via 'netstat -an' or 'tmsh list sys httpd' to find exposed service ports)Affected if Statistics service ports are listening and reachable on the network
-
Verify if TLS encryption is enforced on stats servicesAttempt to connect to the statistics endpoint using HTTP (not HTTPS) or inspect the service configuration to determine if TLS/SSL is not being used (check for 'ssl' or 'tls' in the service binding configuration)Affected if The statistics services accept plaintext HTTP connections or do not require TLS for communication
-
Confirm network accessibility of unauthenticated stats endpointsFrom an external host on the network, attempt to access the statistics endpoint without providing any credentials (e.g., curl http://<BIG-IQ-IP>:<port>/mgmt/shared/stats or similar)Affected if Sensitive statistical data is returned without requiring authentication credentials
You are affected if your BIG-IQ version is between 6.0.0 and 6.1.0 AND the statistics services are network-accessible without requiring authentication or TLS encryption.
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 dataUpgrade BIG-IQ to a version beyond 6.1.0 that includes proper authentication and TLS encryption for stats services. If immediate upgrade is not feasible, restrict network access to stats service ports via firewall rules to prevent unauthorized external access.
Fix this in Big Iq Centralized Management
Scoped from the published advisory
- Consultation3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6652 — 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-6652 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