Elastic Services ControllerApplication · Cisco
CVE-2017-6697
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 web interface of Cisco Elastic Services Controllers could allow an authenticated, remote attacker to access sensitive system credentials that are stored in an affected system. More Information: CSCvd76339. Known Affected Releases: 2.2(9.76).
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 confidenceInsufficient information provided - the official description indicates a vulnerability in the web interface of Cisco Elastic Services Controllers allows an authenticated, remote attacker to access sensitive system credentials stored on the affected system. The specific attack vector, vulnerable code paths, and exact nature of the credential exposure are not detailed in the provided material.
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
Elastic Services ControllerApplication
= 2.2\(9.76\)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
- None
- Availability
- None
CVSS:3.0/AV:N/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 Cisco ESC installationLocate the Cisco Elastic Services Controller in your environment. This is typically deployed as a virtual machine or appliance. Check network inventories or VM inventories for systems running Cisco ESC.Affected if Cisco Elastic Services Controller is present in the environment
-
Check installed ESC versionAccess the ESC CLI or admin web interface and retrieve the software version. The command may vary but typically involves showing the version or checking the about/settings page. Compare the version to 2.2(9.76).Affected if The installed version is exactly 2.2(9.76)
-
Verify web interface is accessibleDetermine if the ESC web interface (typically HTTPS on port 443 or 8443) is exposed and reachable from network locations. Check firewall rules, ACLs, or accessible IP addresses.Affected if The ESC web interface is accessible from any network location beyond trusted administrators
-
Confirm authentication methodReview whether default credentials, weak credentials, or shared accounts exist for ESC web interface access. Check if the authentication mechanism allows remote login.Affected if Remote authentication to the web interface is enabled with any valid user account
You are affected if Cisco Elastic Services Controller version 2.2(9.76) is installed AND its web interface is accessible to authenticated users, allowing them to retrieve stored system credentials.
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 for CSCvd76339 or upgrade to a Cisco ESC version beyond the known affected release 2.2(9.76). If a patch is unavailable, restrict web interface access to trusted users via network segmentation and enforce strong authentication.
Fix this in Elastic Services Controller
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.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 $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-6697 — 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-6697 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