# CVE-2017-6709: Information disclosure in Cisco Ultra Services Framework

> Unauthenticated attackers can access administrative credentials stored in clear text within log files of the Cisco Ultra Services Framework AutoVNF tool.

- **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-h756-wcv2-r9g9

## What is CVE-2017-6709?

CVE-2017-6709 is a critical vulnerability in Cisco Ultra Services Framework, 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 AutoVNF tool for the Cisco Ultra Services Framework could allow an unauthenticated, remote attacker to access administrative credentials for Cisco Elastic Services Controller (ESC) and Cisco OpenStack deployments in an affected system. The vulnerability exists because the affected software logs administrative credentials in clear text for Cisco ESC and Cisco OpenStack deployment purposes. An attacker could exploit this vulnerability by accessing the AutoVNF URL for the location where the log files are stored and subsequently accessing the administrative credentials that are stored in clear text in those log files. This vulnerability affects all releases of the Cisco Ultra Services Framework prior to Releases 5.0.3 and 5.1. Cisco Bug IDs: CSCvc76659.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File), CWE-522 (Insufficiently Protected Credentials), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Cisco Ultra Services Framework.

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

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

## Is CVE-2017-6709 being exploited?

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

## Other vulnerabilities in Cisco Ultra Services Framework

- [CVE-2017-6708](https://insights.sbomify.com/CVE-2017-6708/): Path traversal in Cisco Ultra Services Framework (critical 9.8)
- [CVE-2017-6711](https://insights.sbomify.com/CVE-2017-6711/): Auth bypass in Cisco Ultra Services Framework (critical 9.1)
- [CVE-2017-6771](https://insights.sbomify.com/CVE-2017-6771/): Information disclosure in Ultra Services Framework (high 7.5)
- [CVE-2017-6680](https://insights.sbomify.com/CVE-2017-6680/): Path traversal in Cisco Ultra Services Framework (high 7.5)
- [CVE-2017-6681](https://insights.sbomify.com/CVE-2017-6681/): Path traversal in Cisco Ultra Services Framework (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-6709 is a critical vulnerability in Cisco Ultra Services Framework, 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-6709 in the wild and no public exploit code.

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

## Sources

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

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