Ultra Services FrameworkApplication · Cisco
CVE-2017-6681
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 VNFStagingView class of Cisco Ultra Services Framework could allow an unauthenticated, remote attacker to execute a relative path traversal attack, enabling an attacker to read sensitive files on the system. More Information: CSCvc76662. Known Affected Releases: 21.0.0.
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 confidenceA path traversal vulnerability exists in the AutoVNF VNFStagingView class of Cisco Ultra Services Framework. An unauthenticated remote attacker can exploit this by using relative path traversal (e.g., ../../../etc/passwd) to access sensitive files outside the intended web root directory. The vulnerability is exploitable without authentication and has a CVSS score of 7.5.
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
= 21.0.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
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 Cisco Ultra Services Framework installationLocate the Cisco Ultra Services Framework installation and determine its version. This is typically found in the product documentation, installation directory, or via CLI commands provided by the product. Query the installed software version using the appropriate method for your deployment (e.g., show version command, installation logs, or software inventory).Affected if The installed version is exactly 21.0.0
-
Confirm AutoVNF component is enabledVerify that the AutoVNF component of Cisco Ultra Services Framework is installed and running. Check the process list, service status, or configuration files that indicate AutoVNF is active in your deployment.Affected if AutoVNF is running and the web interface (VNFStagingView) is accessible over the network
-
Check network exposure of VNFStagingViewDetermine if the AutoVNF web interface (specifically the VNFStagingView endpoint) is accessible from the network. This typically involves checking firewall rules, reverse proxy configurations, or listening network services on the port used by AutoVNF (consult product documentation for default port).Affected if The VNFStagingView endpoint is reachable over HTTP/HTTPS without authentication
-
Test for path traversal accessUsing a web request tool, attempt a relative path traversal request to the VNFStagingView endpoint such as ../../../etc/passwd or similar patterns to verify if file access outside the web root is possible. Observe if the response contains contents of files outside the intended directory.Affected if The application returns file contents from outside the web root directory, confirming the path traversal vulnerability is exploitable
You are affected if Cisco Ultra Services Framework version 21.0.0 is installed AND the AutoVNF VNFStagingView web interface is network-accessible and responds to path traversal requests.
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 the vendor patch when available. In the interim, restrict network access to the AutoVNF component and implement web application firewall rules to block path traversal patterns.
Fix this in Ultra Services Framework
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.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 $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-6681 — 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-6681 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