dbcve.org
Ultra Services Framework Element ManagerApplication · Cisco

CVE-2017-6687

HIGH · 8.8 CVSS v3.0 Published 2017-06-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 Cisco Ultra Services Framework Element Manager could allow an authenticated, remote attacker with access to the management network to log in to the affected device using default credentials present on the system, aka an Insecure Default Password Vulnerability. More Information: CSCvc76695. 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 confidence

This is a default credential vulnerability in Cisco Ultra Services Framework Element Manager (release 21.0.0). An authenticated attacker with access to the management network can exploit hardcoded default credentials present on the system to gain unauthorized access to the affected device.

MitigationImmediately change all default credentials on affected systems, restrict management interface access to authorized personnel only via network segmentation, and implement a credential management policy to prevent future use of default passwords.

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 Framework Element ManagerApplication
Affected:= 21.0.0

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:L/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 checks

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

  1. Identify Cisco Ultra Services Framework Element Manager installation
    Check the installed version of Cisco Ultra Services Framework Element Manager by running: 'rpm -q usf-element-manager' or 'dpkg -l | grep usf-element-manager' depending on your Linux distribution
    Affected if The installed version is 21.0.0 exactly
  2. Locate management interface configuration files
    Search for configuration files in typical Cisco management directories such as /opt/cisco/usf/em/ or /etc/usf/ and look for XML or properties files containing credential or user definitions
    Affected if Default credential entries are found in configuration or credential storage files
  3. Test default credentials against the management interface
    Attempt to authenticate to the Element Manager web interface or CLI using known default username/password combinations for version 21.0.0 (consult Cisco documentation for the specific default credentials for this release)
    Affected if Authentication succeeds with default credentials that have not been changed
  4. Check network accessibility of management ports
    Verify which network interfaces the management service is bound to using 'netstat -tlnp | grep -i usf' or 'ss -tlnp | grep -i usf' to determine if it listens on all interfaces or only localhost
    Affected if The management interface is accessible from network segments other than a dedicated management VLAN
  5. Review authentication logs for default account usage
    Examine authentication and system logs in /var/log/ or the Element Manager log directory for entries indicating successful logins using default or administrative accounts
    Affected if Logs show recent successful authentications using factory-default credentials

You are affected if Cisco Ultra Services Framework Element Manager version 21.0.0 is installed AND default credentials remain unchanged AND the management interface is accessible from your network.

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

Immediately change all default credentials on affected systems, restrict management interface access to authorized personnel only via network segmentation, and implement a credential management policy to prevent future use of default passwords.

Fix this in Ultra Services Framework Element Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-6687 — 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-6687 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