# CVE-2017-6713: Hardcoded credentials in Cisco Elastic Services Controller

> Unauthenticated attackers can use static default credentials to gain full administrative access to the Cisco Elastic Services Controller web interface.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-96vr-63hc-8mgg

## What is CVE-2017-6713?

CVE-2017-6713 is a critical vulnerability in Cisco Elastic Services Controller, published on 6 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the Play Framework of Cisco Elastic Services Controller (ESC) could allow an unauthenticated, remote attacker to gain full access to the affected system. The vulnerability is due to static, default credentials for the Cisco ESC UI that are shared between installations. An attacker who can extract the static credentials from an existing installation of Cisco ESC could generate an admin session token that allows access to all instances of the ESC web UI. This vulnerability affects Cisco Elastic Services Controller prior to releases 2.3.1.434 and 2.3.2. Cisco Bug IDs: CSCvc76627.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-264

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

It affects 1 product.


Products: Cisco Elastic Services Controller.

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

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

## Is CVE-2017-6713 being exploited?

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

## Other vulnerabilities in Cisco 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-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)
- [CVE-2017-6683](https://insights.sbomify.com/CVE-2017-6683/): Command injection in Cisco Elastic Services Controller (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-6713 is a critical vulnerability in Cisco Elastic Services Controller, published on 6 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-6713 in the wild and no public exploit code.

Affected product: Cisco 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-6713/ (Markdown: https://insights.sbomify.com/CVE-2017-6713/index.md)
```

## Sources

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

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