Elastic Services ControllerApplication · Cisco
CVE-2017-6682
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 run arbitrary commands as the Linux tomcat user on an affected system. More Information: CSCvc76620. 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 · high confidenceCommand injection vulnerability in the ConfD CLI of Cisco Elastic Services Controllers allows an authenticated, remote attacker to execute arbitrary commands as the Linux tomcat user on affected systems. The attacker needs valid credentials to access the CLI, but can then inject OS commands through insufficient input sanitization.
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
- 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 Cisco ESC versionLog into the Cisco Elastic Services Controller and run 'show version' or check the installed package version using the system package manager. Alternatively, check the /opt/cisco/esc/esc_version file if it exists on the system.Affected if The installed version is exactly 2.2(9.76)
-
Verify ConfD CLI is enabledCheck if the ConfD CLI service is running and accessible. Look for the ConfD process using 'ps aux | grep confd' or check the configuration files in /etc/confd/ or /opt/cisco/confd/ directory.Affected if ConfD CLI process is running and the CLI port (typically 2024 or 2024) is open and listening
-
Confirm CLI network accessibilityRun 'netstat -tuln | grep -E "(2024|2024)"' or use 'ss -tuln' to check if the ConfD CLI port is exposed on a network interface. Verify if it binds to 0.0.0.0 or an external IP rather than localhost only.Affected if The ConfD CLI port is listening on a reachable network interface (not localhost only)
-
Check for existing user accountsReview the ConfD CLI user database or AAA configuration to enumerate valid user accounts. Check /etc/passwd for tomcat user and verify if ConfD users exist with administrative privileges.Affected if There are active ConfD CLI user accounts with valid credentials (the vulnerability requires authenticated access)
A system is affected if it runs Cisco Elastic Services Controller version 2.2(9.76) AND has the ConfD CLI enabled and network-accessible, allowing an attacker with valid credentials to inject commands.
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 available Cisco software updates for the Elastic Services Controller. If no update is available, implement strict input validation and command whitelisting in the ConfD CLI, and restrict CLI access to minimal necessary personnel.
Fix this in Elastic Services Controller
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-6682 — 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-6682 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