Meeting ServerApplication · Cisco
CVE-2017-12224
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 · uneditedA vulnerability in the ability for guest users to join meetings via a hyperlink with Cisco Meeting Server could allow an authenticated, remote attacker to enter a meeting with a hyperlink URL, even though access should be denied. The vulnerability is due to the incorrect implementation of the configuration setting Guest access via hyperlinks, which should allow the administrative user to prevent guest users from using hyperlinks to connect to meetings. An attacker could exploit this vulnerability by using a crafted hyperlink to connect to a meeting. An exploit could allow the attacker to connect directly to the meeting with a hyperlink, even though access should be denied. The attacker would still require a valid hyperlink and encoded secret identifier to be connected. Cisco Bug IDs: CSCve20873.
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 confidenceThis is a configuration bypass vulnerability in Cisco Meeting Server where the 'Guest access via hyperlinks' setting is incorrectly implemented, allowing authenticated remote attackers to join meetings via hyperlink URLs even when this access should be denied. The attacker requires a valid hyperlink with an encoded secret identifier to exploit this vulnerability.
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
Meeting ServerApplication
all versionsCVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Cisco Meeting Server installationCheck if Cisco Meeting Server is running in your environment by querying for the 'cms' or 'Cisco Meeting Server' process/service, or reviewing installed software inventoryAffected if Cisco Meeting Server is present in the environment
-
Locate the Guest access via hyperlinks configurationAccess the Cisco Meeting Server admin interface or configuration files and navigate to the settings panel containing 'Guest access via hyperlinks' or similar terminologyAffected if This specific setting exists and can be configured in your deployment
-
Verify the current Guest access via hyperlinks settingInspect the current state of the Guest access via hyperlinks toggle or checkbox in the CMS admin interfaceAffected if Guest access via hyperlinks is enabled (set to allow/yes/true)
-
Check for active meeting hyperlinksReview meeting configurations, recorded meetings, or calendar integrations for any generated hyperlink URLs containing encoded identifiers (typically in format similar to https://domain.meeting/call/XXXXX)Affected if Active hyperlinks with embedded secret identifiers exist in the system
-
Audit recent meeting join eventsReview meeting server logs or audit trails for unexpected join events, particularly from external IP addresses or anonymous/guest users joining via hyperlinks when access should be deniedAffected if There are join events from guests via hyperlinks occurring outside expected parameters
You are affected if Cisco Meeting Server is running and Guest access via hyperlinks is enabled, regardless of intended access controls, as the bypass allows unauthorized guest access via valid hyperlinks.
Generated from the published advisory. Verify against your own configuration.
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 dataAdministrators should review and properly configure the 'Guest access via hyperlinks' setting in Cisco Meeting Server, and apply any available software updates that correctly enforce this access control.
Fix this in Meeting Server
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12224 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-12224 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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