dbcve.org
Ultra Services FrameworkApplication · Cisco

CVE-2017-6771

HIGH · 7.5 CVSS v3.0 Published 2017-08-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
A vulnerability in the AutoVNF automation tool of the Cisco Ultra Services Framework could allow an unauthenticated, remote attacker to acquire sensitive information. The vulnerability is due to insufficient protection of sensitive data. An attacker could exploit this vulnerability by browsing to a specific URL of an affected device. An exploit could allow the attacker to view sensitive configuration information about the deployment. Cisco Bug IDs: CSCvd29358. Known Affected Releases: 21.0.v0.65839.

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 confidence

The Cisco Ultra Services Framework AutoVNF automation tool contains a vulnerability allowing unauthenticated remote attackers to view sensitive deployment configuration information by directly browsing to specific URLs. This is due to insufficient protection of sensitive data within the AutoVNF interface.

MitigationApply the Cisco patch for bug CSCvd29358 when available, or implement strict network access controls to restrict unauthorized access to the AutoVNF management interface.

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
Affected:= 21.0.v0.65839

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Cisco Ultra Services Framework installation
    Locate and identify any Cisco Ultra Services Framework deployment in your environment. Check for processes or services named AutoVNF or related Ultra Services components.
    Affected if Cisco Ultra Services Framework with AutoVNF component is present
  2. Check installed version
    Query the installed version of Cisco Ultra Services Framework. The exact version is 21.0.v0.65839. Use vendor-provided commands or configuration files to determine the running version.
    Affected if Installed version equals 21.0.v0.65839
  3. Verify AutoVNF web interface exposure
    Determine if the AutoVNF web management interface is network-accessible. Check firewall rules, ACLs, and network configuration to see if the AutoVNF HTTP/HTTPS ports are exposed to unauthorized networks or the internet.
    Affected if AutoVNF interface is accessible from untrusted networks without authentication
  4. Confirm no authentication required for sensitive URLs
    Test whether sensitive configuration endpoints on the AutoVNF interface can be accessed without credentials. Attempt to browse to the AutoVNF URLs directly without providing any authentication.
    Affected if Sensitive deployment configuration information is accessible without authentication

You are affected if Cisco Ultra Services Framework version 21.0.v0.65839 is installed AND the AutoVNF interface is network-accessible to untrusted users without authentication controls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Cisco patch for bug CSCvd29358 when available, or implement strict network access controls to restrict unauthorized access to the AutoVNF management interface.

Fix this in Ultra Services Framework Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-6771 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-6771 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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