dbcve.org
Webex Meetings ServerApplication · Cisco

CVE-2017-3880

MEDIUM · 6.5 CVSS v3.0 Published 2017-03-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
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
An Authentication Bypass vulnerability in Cisco WebEx Meetings Server could allow an unauthenticated, remote attacker to access limited meeting information on the Cisco WebEx Meetings Server. More Information: CSCvd50728. Known Affected Releases: 2.6 2.7 2.8 CWMS-2.5MR1 Orion1.1.2.patch T29_orion_merge.

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 authentication bypass vulnerability in Cisco WebEx Meetings Server allows unauthenticated remote attackers to access limited meeting information without credentials. The vulnerability stems from insufficient authentication checks on certain API endpoints, enabling enumeration and disclosure of meeting metadata.

MitigationApply vendor-provided patches or updates from Cisco for all affected versions (2.5MR1 through 2.8). If patches are unavailable, implement network segmentation to restrict unauthorized access to the meeting server and monitor for anomalous access patterns.

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
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 administrative interface or check system documentation/configuration files for the installed version number. Typical locations include the admin console, systeminfo endpoint, or installation records.
    Affected if The installed version matches one of the affected versions: 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, or 2.6.1.39
  2. Verify API endpoint accessibility
    Attempt to access the meeting API endpoints without providing authentication credentials. Common endpoints include those related to meeting metadata, attendee information, or recording listings.
    Affected if The API endpoints respond with meeting information or metadata without requiring any authentication tokens or credentials
  3. Review access logs for unauthenticated API requests
    Examine server access logs, web server logs, or security event logs for requests to API endpoints that lack authentication headers or session tokens.
    Affected if Logs show requests to meeting API endpoints originating from unauthenticated or unknown external IP addresses
  4. Check for anomalous meeting enumeration activity
    Search logs for patterns indicating meeting ID enumeration, such as sequential requests to different meeting identifiers or excessive 200 OK responses on unauthenticated API calls.
    Affected if Unauthenticated enumeration attempts are observed or meeting metadata is retrievable without credentials

A system is affected if it runs any of the listed Cisco WebEx Meetings Server versions AND has API endpoints accessible without authentication, allowing unauthorized meeting metadata disclosure.

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

Apply vendor-provided patches or updates from Cisco for all affected versions (2.5MR1 through 2.8). If patches are unavailable, implement network segmentation to restrict unauthorized access to the meeting server and monitor for anomalous access patterns.

Fix this in Webex Meetings Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-3880 — 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-3880 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