# CVE-2017-6777: Information disclosure in Elastic Services Controller

> An authenticated attacker can view sensitive configuration parameters in Cisco Elastic Services Controller, potentially exposing system details.

- **Severity:** Medium 4.9 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Aug 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-pqcm-92mq-2rgw

## What is CVE-2017-6777?

CVE-2017-6777 is a medium-severity vulnerability in Cisco Systems, Inc. Elastic Services Controller, published on 17 Aug 2017. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability in the ConfD server of the Cisco Elastic Services Controller (ESC) could allow an authenticated, remote attacker to acquire sensitive system information. The vulnerability is due to insufficient protection of sensitive files on the system. An attacker could exploit this vulnerability by logging into the ConfD server and executing certain commands. An exploit could allow an unprivileged user to view configuration parameters that can be maliciously used. Cisco Bug IDs: CSCvd76409. Known Affected Releases: 2.3, 2.3(2).

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2017-6777?

It affects 1 product.


Products: Cisco Elastic Services Controller.

## How do I fix CVE-2017-6777?

No fix has been published for CVE-2017-6777 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-6777 being exploited?

There is no known exploitation of CVE-2017-6777 in the wild and no public exploit code.

## Other vulnerabilities in Cisco Systems, Inc. Elastic Services Controller

- [CVE-2019-1867](https://insights.sbomify.com/CVE-2019-1867/): Cisco Elastic Services Controller REST API Authentication Bypass Vulnerability (critical 10.0)
- [CVE-2018-0121](https://insights.sbomify.com/CVE-2018-0121/): Auth bypass in Cisco Elastic Services Controller (critical 9.8)
- [CVE-2017-6713](https://insights.sbomify.com/CVE-2017-6713/): Hardcoded credentials in Cisco Elastic Services Controller (critical 9.8)
- [CVE-2017-6712](https://insights.sbomify.com/CVE-2017-6712/): Command injection in Cisco Elastic Services Controller (high 8.8)
- [CVE-2017-6682](https://insights.sbomify.com/CVE-2017-6682/): Command injection in Cisco Elastic Services Controller (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-6777 and fix it if it is affected.

What it is: CVE-2017-6777 is a medium-severity vulnerability in Cisco Systems, Inc. Elastic Services Controller, published on 17 Aug 2017. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-6777 in the wild and no public exploit code.

Affected product: Cisco Systems, Inc. Elastic Services Controller. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-6777/ (Markdown: https://insights.sbomify.com/CVE-2017-6777/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-6777
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-6777
- OSV: https://osv.dev/vulnerability/CVE-2017-6777

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-6777/
Summaries are generated and may contain mistakes; the official description above is the record.