Webex Meetings ServerApplication · Cisco

CVE-2017-12363

MEDIUM · 5.3 CVSS v3.0 Published 2017-11-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/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
A vulnerability in Cisco WebEx Meeting Server could allow an unauthenticated, remote attacker to modify the welcome message of a meeting on an affected system. The vulnerability is due to insufficient security settings on meetings. An attacker could exploit this vulnerability by modifying the welcome message to a meeting. A successful exploit could allow the attacker to modify the welcome message of any known meeting. Cisco Bug IDs: CSCvf68695.

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

A vulnerability in Cisco WebEx Meeting Server allows an unauthenticated, remote attacker to modify the welcome message of any known meeting due to insufficient security settings on meetings. The attacker can exploit this by directly modifying the meeting welcome message without any authentication, potentially impersonating legitimate meeting organizers.

MitigationApply the Cisco patch for bug CSCvf68695 and review meeting security configurations to ensure meetings require appropriate authentication and authorization controls.

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.6.0.8= 2.7

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 Cisco WebEx Meeting Server installation
    Locate the Cisco WebEx Meeting Server components on the system or check the product inventory. Look for WebEx Meeting Server services, binaries, or management interfaces.
    Affected if Cisco WebEx Meeting Server is present on the network or system
  2. Determine installed version
    Use the system's version reporting mechanism or administrative interface to obtain the exact version number of the Cisco WebEx Meeting Server installation. Compare against the affected versions 2.6.0.8 and 2.7.
    Affected if The installed version is 2.6.0.8 or 2.7
  3. Review meeting access controls
    Access the meeting server administration console or configuration files. Examine the security settings for existing meetings to determine if unauthenticated access is permitted for modifying meeting properties.
    Affected if Meetings are configured to allow unauthenticated users to modify meeting welcome messages or other meeting properties
  4. Verify meeting authentication requirements
    Check the authentication and authorization settings for meetings. Look for settings that control whether users must authenticate before they can modify meeting configurations or welcome messages.
    Affected if Meetings lack proper authentication requirements and allow anonymous or unauthenticated modifications

You are affected if Cisco WebEx Meeting Server versions 2.6.0.8 or 2.7 are installed AND meetings are configured without authentication controls that would prevent unauthenticated modification of welcome messages.

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 the Cisco patch for bug CSCvf68695 and review meeting security configurations to ensure meetings require appropriate authentication and authorization controls.

Fix this in Webex Meetings Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-12363 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