Ultra Services PlatformApplication · Cisco
CVE-2017-6694
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 Virtual Network Function Manager's (VNFM) logging function of Cisco Ultra Services Platform could allow an authenticated, local attacker to view sensitive data (cleartext credentials) on an affected system. More Information: CSCvd29355. 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 · high confidenceA vulnerability in the Virtual Network Function Manager (VNFM) logging function of Cisco Ultra Services Platform allows authenticated local attackers to view cleartext credentials in log files. The logging function fails to mask or encrypt sensitive authentication data before writing to logs.
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 PlatformApplication
= 21.0.v0.65839CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:L/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 installed Cisco Ultra Services Platform versionRun 'show version' or check /opt/usp/version file to determine the exact installed version of Cisco Ultra Services PlatformAffected if Installed version equals 21.0.v0.65839 exactly
-
Locate VNFM log filesNavigate to the VNFM logging directory, typically found under /var/log/usp/vnfm/ or check the logging configuration file for configured log pathsAffected if VNFM log files exist on the system
-
Search VNFM logs for cleartext credentialsUse grep or a text search tool to search VNFM log files for patterns resembling usernames and passwords, such as 'password=', 'pwd=', 'user=', or credential-like strings in plain textAffected if Log files contain unencrypted credential strings such as 'password=...' or 'pwd=...' in cleartext
-
Verify VNFM logging function is activeCheck if the VNFM component is running and logging is enabled by reviewing the VNFM process status and associated logging configuration filesAffected if VNFM logging is enabled and the component is actively writing logs
-
Inspect recent log entries for authentication dataExamine the most recent VNFM log files (sorted by modification time) for any logged authentication operations that may contain sensitive credential information in plain textAffected if Recent VNFM logs show authentication events with visible passwords or credentials
A system is affected if it runs Cisco Ultra Services Platform version 21.0.v0.65839 and VNFM logs contain cleartext credentials from authentication operations.
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 dataImplement credential masking or complete exclusion of sensitive data from all VNFM logging functions; review and purge existing logs containing cleartext credentials.
Fix this in Ultra Services Platform
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-6694 — 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-6694 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