# CVE-2017-6640: Hardcoded credentials in Cisco Prime Data Center Network Manager Server Static Credential Vulnerability

> An unauthenticated remote attacker can log in to the administrative console using a default static password, gaining root-level privileges.

- **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:** 8 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-f699-hchg-47fv

## What is CVE-2017-6640?

CVE-2017-6640 is a critical vulnerability in Cisco Prime Data Center Network Manager Server Static Credential Vulnerability, published on 8 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in Cisco Prime Data Center Network Manager (DCNM) Software could allow an unauthenticated, remote attacker to log in to the administrative console of a DCNM server by using an account that has a default, static password. The account could be granted root- or system-level privileges. The vulnerability exists because the affected software has a default user account that has a default, static password. The user account is created automatically when the software is installed. An attacker could exploit this vulnerability by connecting remotely to an affected system and logging in to the affected software by using the credentials for this default user account. A successful exploit could allow the attacker to use this default user account to log in to the affected software and gain access to the administrative console of a DCNM server. This vulnerability affects Cisco Prime Data Center Network Manager (DCNM) Software releases prior to Release 10.2(1) for Microsoft Windows, Linux, and Virtual Appliance platforms. Cisco Bug IDs: CSCvd95346.

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

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

It affects 1 product.


Products: Cisco Prime Data Center Network Manager.

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

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

## Is CVE-2017-6640 being exploited?

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

Public exploit code:

- Proof of concept for CVE-2017-6640 as burp extension (github_poc): https://github.com/hemp3l/CVE-2017-6640-POC

## Other vulnerabilities in Cisco Prime Data Center Network Manager Server Static Credential Vulnerability

- [CVE-2015-0666](https://insights.sbomify.com/CVE-2015-0666/): Cisco Prime Data Center Network Manager (DCNM) Directory Traversal (high 7.5, exploited in the wild)
- [CVE-2013-5486](https://insights.sbomify.com/CVE-2013-5486/): Path traversal in n/a (critical 10.0)
- [CVE-2012-5417](https://insights.sbomify.com/CVE-2012-5417/): Missing authorization in n/a (critical 10.0)
- [CVE-2018-0258](https://insights.sbomify.com/CVE-2018-0258/): File upload in Cisco Prime File Upload Servlet (critical 9.8)
- [CVE-2017-6639](https://insights.sbomify.com/CVE-2017-6639/): Missing authorization in Cisco Prime Data Center Network Manager Debug Remote Code Execution Vulnerability (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-6640 is a critical vulnerability in Cisco Prime Data Center Network Manager Server Static Credential Vulnerability, published on 8 Jun 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-6640 in the wild and no public exploit code.

Affected product: Cisco Prime Data Center Network Manager Server Static Credential Vulnerability. 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-6640/ (Markdown: https://insights.sbomify.com/CVE-2017-6640/index.md)
```

## Sources

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

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