dbcve.org
Webex Meetings ServerApplication · Cisco

CVE-2017-6651

HIGH · 7.5 CVSS v3.0 Published 2017-05-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

An information disclosure vulnerability in Cisco WebEx Meetings Server allows unauthenticated remote attackers to access scheduled meeting information via an exposed parameter that searches indexed meeting data. The vulnerability stems from an incomplete robots.txt configuration on customer-hosted WebEx solutions when the Short URL functionality is not activated. Affected versions are 2.5, 2.6, 2.7, and 2.8.

MitigationEnable the Short URL functionality in Cisco WebEx Meetings Server or upgrade to a release later than 2.5MR4 where this functionality is provided, and ensure proper robots.txt configuration is applied to prevent search engine indexing of meeting information.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Webex Meetings ServerApplication
Affected:= 2.5.1.5= 2.5.1.29= 2.5.99.2= 2.5_base= 2.5_mr1= 2.5_mr2= 2.5_mr3= 2.5_mr4= 2.5_mr5= 2.5_mr6= 2.6.0= 2.6.1.39

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Cisco WebEx Meetings Server version
    Access the WebEx admin interface and navigate to the version or system information section, or check the installed package version via system documentation
    Affected if The installed version matches 2.5.x, 2.6.x, 2.7.x, or 2.8.x (specifically 2.5.1.5, 2.5.1.29, 2.5.99.2, 2.5_base, 2.5_mr1-mr6, 2.6.0, or 2.6.1.39)
  2. Verify Short URL functionality status
    Access the WebEx server admin settings and locate the Short URL or URL Shortening configuration option. Check whether this feature is enabled or disabled
    Affected if The Short URL functionality is disabled or not activated in the configuration
  3. Inspect robots.txt file for completeness
    Retrieve the robots.txt file from the WebEx server root (for example, https://your-webex-server.example.com/robots.txt) and examine the directives
    Affected if The robots.txt file is missing, incomplete, or does not contain proper Disallow directives to prevent search engine indexing of meeting-related URLs or parameters

A user is affected if the installed version is 2.5, 2.6, 2.7, or 2.8, Short URL functionality is disabled, and robots.txt is missing or incomplete.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Enable the Short URL functionality in Cisco WebEx Meetings Server or upgrade to a release later than 2.5MR4 where this functionality is provided, and ensure proper robots.txt configuration is applied to prevent search engine indexing of meeting information.

Fix this in Webex Meetings Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-6651 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-6651 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data