# CVE-2017-6651: Information disclosure in Cisco WebEx Meetings Server

> Unauthenticated attackers can access scheduled meeting details via exposed parameters when Short URL functionality is disabled, potentially allowing unauthorized meeting attendance.

- **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:** 16 May 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7mmm-cmfg-5466

## What is CVE-2017-6651?

CVE-2017-6651 is a high-severity vulnerability in Cisco Webex Meetings Server, published on 16 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in Cisco WebEx Meetings Server could allow unauthenticated, remote attackers to gain information that could allow them to access scheduled customer meetings. The vulnerability is due to an incomplete configuration of the robots.txt file on customer-hosted WebEx solutions and occurs when the Short URL functionality is not activated. All releases of Cisco WebEx Meetings Server later than release 2.5MR4 provide this functionality. An attacker could exploit this vulnerability via an exposed parameter to search for indexed meeting information. A successful exploit could allow the attacker to obtain scheduled meeting information and potentially allow the attacker to attend scheduled, customer meetings. This vulnerability affects the following releases of Cisco WebEx Meetings Server: 2.5, 2.6, 2.7, 2.8. Cisco Bug IDs: CSCve25950.

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

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

It affects 1 product.


Products: Cisco Webex Meetings Server.

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

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

## Is CVE-2017-6651 being exploited?

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

## Other vulnerabilities in Cisco Webex Meetings Server

- [CVE-2017-12367](https://insights.sbomify.com/CVE-2017-12367/): Memory corruption in Cisco WebEx Recording Format and Advanced Recording Format Players (critical 9.6)
- [CVE-2015-0589](https://insights.sbomify.com/CVE-2015-0589/): Command injection in n/a (critical 9.0)
- [CVE-2017-3794](https://insights.sbomify.com/CVE-2017-3794/): Cross-site request forgery in Cisco WebEx Meetings Server 2.6 (high 8.8)
- [CVE-2016-1448](https://insights.sbomify.com/CVE-2016-1448/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2016-1446](https://insights.sbomify.com/CVE-2016-1446/): SQL injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-6651 is a high-severity vulnerability in Cisco Webex Meetings Server, published on 16 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-6651 in the wild and no public exploit code.

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

## Sources

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

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