Ultra Services FrameworkApplication · Cisco
CVE-2017-6709
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 AutoVNF tool for the Cisco Ultra Services Framework could allow an unauthenticated, remote attacker to access administrative credentials for Cisco Elastic Services Controller (ESC) and Cisco OpenStack deployments in an affected system. The vulnerability exists because the affected software logs administrative credentials in clear text for Cisco ESC and Cisco OpenStack deployment purposes. An attacker could exploit this vulnerability by accessing the AutoVNF URL for the location where the log files are stored and subsequently accessing the administrative credentials that are stored in clear text in those log files. This vulnerability affects all releases of the Cisco Ultra Services Framework prior to Releases 5.0.3 and 5.1. Cisco Bug IDs: CSCvc76659.
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 AutoVNF tool in Cisco Ultra Services Framework stores administrative credentials for Cisco Elastic Services Controller (ESC) and Cisco OpenStack deployments in clear text within log files. An unauthenticated, remote attacker can access these log files by navigating to the AutoVNF URL, exposing credentials that grant access to affected system components.
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
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 if Cisco Ultra Services Framework is installedLocate the Cisco Ultra Services Framework installation directory or check system inventory for this productAffected if The product is present on the system
-
Determine the installed version of Cisco Ultra Services FrameworkUse the product's version command or check version files within the installation directoryAffected if The version is 5.0.2 or earlier (any version up to and including 5.0.2)
-
Verify if AutoVNF component is enabled and accessibleCheck if the AutoVNF web interface or API endpoint is reachable on the networkAffected if AutoVNF is exposed and accessible to network users
-
Inspect AutoVNF log files for credential exposureLocate and examine log files generated by the AutoVNF tool, looking for stored ESC or OpenStack credentials in clear textAffected if Log files contain readable administrative credentials for ESC or Cisco OpenStack deployments
A user is affected if Cisco Ultra Services Framework version 5.0.2 or earlier is installed and AutoVNF log files are accessible, exposing credentials in clear text.
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 to Cisco Ultra Services Framework Releases 5.0.3 or 5.1 or later. Additionally, restrict network access to the AutoVNF URL and log file directories to prevent unauthorized access until patching is complete.
Cisco Ultra Services Framework Release 5.0.3 or 5.1
- Review Cisco Ultra Services Framework release notes for versions 5.0.3 and 5.1 to understand changes and prerequisites
- Download the fixed release (5.0.3 or 5.1) from Cisco's official download site
- Follow Cisco's documented upgrade procedure to update Ultra Services Framework to the fixed version
- After upgrade, verify the fix by confirming that credential information is no longer exposed in AutoVNF log files
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Ultra Services Framework
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-6709 — 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-6709 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