Elastic Services ControllerApplication · Cisco
CVE-2017-6693
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 server component of Cisco Elastic Services Controllers could allow an authenticated, local attacker to access information stored in the file system of an affected system, aka Unauthorized Directory Access. More Information: CSCvd76286. Known Affected Releases: 2.2(9.76) 2.3(1).
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 confidenceThe ConfD server component in Cisco Elastic Services Controllers contains an unauthorized directory access vulnerability that allows an authenticated local attacker to read files and directories outside the intended scope. An attacker with valid credentials could exploit this to gather sensitive information from the host file system.
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\)= 2.3\(1\)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
- 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 the installed productConfirm the system is running Cisco Elastic Services Controller (ESC). Check the product name via 'show version' or system inventory.Affected if The product is not Cisco Elastic Services Controller, this CVE does not apply.
-
Determine the ESC software versionRun 'show version' or check the installed package version to identify the exact ESC release (for example, 2.2(9.76) or 2.3(1)). Compare against the affected versions.Affected if The installed version is exactly 2.2(9.76) or exactly 2.3(1). Versions outside these two releases are not affected by this specific CVE.
-
Verify the ConfD server component is presentCheck if the ConfD server (part of the ESC management stack) is installed and running. Look for ConfD processes or configuration files in the ESC installation directory.Affected if ConfD is not installed or not in use, the vulnerability cannot be exploited against this system.
-
Check for local authentication configurationReview the ESC user authentication settings to determine if local user accounts are configured. Examine the user database or authentication configuration files.Affected if Local authentication is enabled and local user accounts exist, an attacker with valid credentials could attempt to exploit the directory traversal flaw.
A system is affected only if it runs Cisco Elastic Services Controller version 2.2(9.76) or 2.3(1), has the ConfD server component enabled, and has local authentication configured with valid user accounts.
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 CSCvd76286 or upgrade to a non-affected release (beyond 2.3(1)). If patching is not immediately possible, restrict local access and monitor for unauthorized file 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-6693 — 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-6693 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