# CVE-2017-6621: Information disclosure in Cisco Prime Collaboration

> Unauthenticated remote attackers can access sensitive system files and user credentials via crafted HTTP requests in Cisco Prime Collaboration Provisioning.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 May 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jv3h-mvmw-qgrw

## What is CVE-2017-6621?

CVE-2017-6621 is a high-severity vulnerability in Cisco Prime Collaboration, published on 18 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the web interface of Cisco Prime Collaboration Provisioning could allow an unauthenticated, remote attacker to access sensitive data. The attacker could use this information to conduct additional reconnaissance attacks. The vulnerability is due to insufficient protection of sensitive data when responding to an HTTP request on the web interface. An attacker could exploit the vulnerability by sending a crafted HTTP request to the application to access specific system files. An exploit could allow the attacker to obtain sensitive information about the application which could include user credentials. This vulnerability affects Cisco Prime Collaboration Provisioning Software Releases 10.6 through 11.5. Cisco Bug IDs: CSCvc99626.

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

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

It affects 1 product.


Products: Cisco Prime Collaboration Provisioning.

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

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

## Is CVE-2017-6621 being exploited?

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

## Other vulnerabilities in Cisco Prime Collaboration

- [CVE-2017-6622](https://insights.sbomify.com/CVE-2017-6622/): Command injection in Cisco Prime Collaboration Provisioning (critical 9.8)
- [CVE-2016-1416](https://insights.sbomify.com/CVE-2016-1416/): Auth bypass in n/a (critical 9.8)
- [CVE-2015-4307](https://insights.sbomify.com/CVE-2015-4307/): Privilege escalation in n/a (critical 9.0)
- [CVE-2017-6756](https://insights.sbomify.com/CVE-2017-6756/): Cross-site request forgery in Cisco Prime Collaboration Provisioning Tool (high 8.8)
- [CVE-2017-12276](https://insights.sbomify.com/CVE-2017-12276/): SQL injection in Cisco Prime Collaboration Provisioning (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-6621 is a high-severity vulnerability in Cisco Prime Collaboration, published on 18 May 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-6621 in the wild and no public exploit code.

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

## Sources

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

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