Elastic Services ControllerApplication · Cisco
CVE-2017-6691
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 ConfD CLI of Cisco Elastic Services Controllers could allow an authenticated, remote attacker to access sensitive information on an affected system. More Information: CSCvd29403. Known Affected Releases: 2.3(2).
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 confidenceThe Cisco Elastic Services Controllers (ESC) contains a vulnerability in its ConfD CLI component that allows an authenticated remote attacker to access sensitive information on the affected system. An attacker with valid credentials can exploit the CLI to view information beyond their intended authorization level. The vulnerability stems from insufficient access controls within the ConfD CLI implementation.
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.3\(2\)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 installationCheck if Cisco Elastic Services Controller is installed in your environment by looking for the ESC web interface or checking installed packages/services named 'elastic-services-controller' or 'esc'Affected if Cisco Elastic Services Controller is present in the environment
-
Verify installed ESC versionAccess the ESC management interface or run 'show version' via CLI to determine the exact ESC version numberAffected if The installed version is exactly 2.3(2)
-
Confirm ConfD CLI access is enabledCheck if the ConfD CLI component is accessible by attempting to access the ESC CLI via SSH or console using valid administrator credentialsAffected if ConfD CLI is accessible and accepts authentication
-
Review user privilege levelsExamine the ConfD CLI user accounts and their assigned privilege levels using 'show users' or similar command within the ESC CLIAffected if Users exist with elevated privileges that may indicate improper access control
-
Audit CLI access logsReview ESC CLI audit logs or system logs for any instances where users accessed information beyond their documented authorization levelAffected if Any log entries show users viewing data outside their intended permission scope
A system is affected if it is running Cisco Elastic Services Controller version 2.3(2) with the ConfD CLI component accessible to authenticated users.
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 Cisco patch for CSCvd29403 or upgrade to a non-vulnerable release. Until a patch is available, restrict CLI access to trusted personnel only and monitor for unauthorized access attempts.
Fix this in Elastic Services Controller
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-6691 — 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-6691 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