Ultra Services FrameworkApplication · Cisco
CVE-2017-6711
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 · uneditedA vulnerability in the Ultra Automation Service (UAS) of the Cisco Ultra Services Framework could allow an unauthenticated, remote attacker to gain unauthorized access to a targeted device. The vulnerability is due to an insecure default configuration of the Apache ZooKeeper service used by the affected software. An attacker could exploit this vulnerability by accessing the affected device through the orchestrator network. An exploit could allow the attacker to gain access to ZooKeeper data nodes (znodes) and influence the behavior of the system's high-availability feature. This vulnerability affects all releases of Cisco Ultra Services Framework UAS prior to Releases 5.0.3 and 5.1. Cisco Bug IDs: CSCvd29395.
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 confidenceThe Cisco Ultra Services Framework UAS contains an insecure default configuration of Apache ZooKeeper that allows unauthenticated remote attackers to access the device via the orchestrator network. Attackers can read and modify ZooKeeper data nodes (znodes), enabling them to manipulate the high-availability feature of the system.
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
Ultra Services FrameworkApplication
<= 5.0.2CVSS 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
- High
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check the installed Cisco Ultra Services Framework UAS versionRun the command to display the UAS software version (typically via CLI command like 'show software version' or check the system banner/About page)Affected if The version displayed is 5.0.2 or earlier (5.0.2, 5.0.1, 5.0.0, etc.)
-
Verify if Apache ZooKeeper is installed and runningCheck for the ZooKeeper process (typically named 'zookeeper' or 'org.apache.zookeeper.server') or check for ZooKeeper configuration files (zoo.cfg) in the UAS installation directoryAffected if ZooKeeper is present and running as part of the UAS deployment
-
Determine if ZooKeeper is bound to an accessible network interfaceInspect ZooKeeper configuration (zoo.cfg) for the 'clientPort' setting and check which IP address it binds to; use 'netstat -anp | grep 2181' (default ZooKeeper port) to verify listening addressesAffected if ZooKeeper is listening on 0.0.0.0 or an IP address accessible from the orchestrator network rather than localhost only
-
Confirm ZooKeeper access controls are disabledReview the ZooKeeper configuration file (zoo.cfg) or check for the absence of JAAS authentication configuration; attempt a ZooKeeper client connection without credentials using 'zkCli.sh -server localhost:2181'Affected if ZooKeeper accepts connections without requiring authentication (no ACL enforcement configured)
-
Assess network exposure of the orchestrator networkReview network segmentation configurations and firewall rules to determine if the ZooKeeper port (default 2181) is accessible from untrusted networks or external interfacesAffected if The ZooKeeper port is reachable from networks outside the trusted orchestrator infrastructure
A user is affected if they are running Cisco Ultra Services Framework UAS version 5.0.2 or earlier AND ZooKeeper is configured without authentication and is accessible from their network.
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.
dbcve · scopedUpgrade Cisco Ultra Services Framework UAS to Releases 5.0.3, 5.1, or later. Additionally, implement network segmentation to restrict access to the orchestrator network and harden ZooKeeper access controls.
Cisco Ultra Services Framework UAS version 5.0.3 or 5.1 (or later)
- 1. Identify the current Cisco Ultra Services Framework UAS version running on the system
- 2. Plan maintenance window as upgrade may require service interruption
- 3. Download Cisco Ultra Services Framework UAS version 5.0.3 or version 5.1 (or later) from Cisco official channels
- 4. Follow Cisco's standard upgrade procedure for Ultra Services Framework UAS
- 5. After upgrade, verify that the Apache ZooKeeper service is now properly secured with authentication
- 6. Confirm the high-availability feature functions correctly post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Ultra Services Framework
Scoped from the published advisory
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-6711 — 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-2017-6711 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