Elastic Services ControllerApplication · Cisco
CVE-2017-6684
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 Cisco Elastic Services Controllers could allow an authenticated, remote attacker to log in to an affected system as the Linux admin user, aka an Insecure Default Credentials Vulnerability. More Information: CSCvc76651. 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 confidenceCisco Elastic Services Controller contains insecure default credentials that allow an authenticated remote attacker to log in to the affected system as the Linux admin user. This is a pre-authentication credential exposure vulnerability where the default administrative credentials are known or easily guessable, enabling unauthorized privilege escalation to root-level access.
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
= 21.0.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Cisco Elastic Services Controller is installedLocate the ESC installation directory or check running processes for ESC-related services. On the system, look for the 'esc' user or group, and check for ESC-specific configuration files in /opt/cisco/esc/ or similar paths.Affected if The system has Cisco Elastic Services Controller installed and is version 21.0.0
-
Determine the installed version of Cisco ESCRun the command 'escadm version' or check /opt/cisco/esc/esc_version file if present. Alternatively, use 'show version' from the ESC CLI if accessible.Affected if The version returned is exactly 21.0.0
-
Check if default credentials are still in useReview system authentication logs for failed login attempts using default usernames such as 'admin', 'root', or 'escadmin'. Verify whether the default password for the admin account has been changed from any documented or known default value.Affected if The default administrative account password has not been changed from the factory default, allowing unauthenticated or authenticated attackers to gain root access
-
Verify management interface accessibilityCheck network configuration to determine if the ESC management interface (typically ports 443 or 22) is exposed to untrusted networks. Review firewall rules and access control lists.Affected if The management interface is reachable from networks other than trusted administrative subnets and default credentials are active
A system is affected if it runs Cisco Elastic Services Controller version 21.0.0 with the default administrative credentials still configured, allowing root-level access to anyone with knowledge of the default 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 dataImmediately change all default credentials to strong, unique passwords following organizational password policies. Restrict network access to the management interface and audit for any unauthorized access attempts using the compromised credentials.
Fix this in Elastic Services Controller
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.0 h
- Testing2.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 $2,592.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-6684 — 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-6684 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