dbcve.org
Telepresence Multipoint SwitchHardware / appliance · Cisco

CVE-2013-5516

MEDIUM · 6.3 CVSS v2.0 Published 2013-10-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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
The Media Snapshot implementation on Cisco TelePresence Multipoint Switch (CTMS) devices allows remote authenticated users to cause a denial of service (device reload) by sending many Media Snapshot requests at the time of a meeting termination, aka Bug ID CSCuh44796.

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

The Media Snapshot feature in Cisco TelePresence Multipoint Switch (CTMS) contains a denial of service vulnerability where remote authenticated users can cause device reload by sending a high volume of Media Snapshot requests specifically during meeting termination. This causes the device to crash and reload, disrupting communications.

MitigationApply the Cisco software update addressing CVE-2013-5516. Additionally, implement rate limiting on Media Snapshot requests at the network edge and monitor for anomalous request patterns during meeting termination events.

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
Telepresence Multipoint SwitchHardware / appliance
Affected:all versions

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
M
Authentication
Single
Confidentiality
None
Integrity
None
Availability
Complete

AV:N/AC:M/Au:S/C:N/I:N/A:C

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. Confirm Cisco TelePresence Multipoint Switch (CTMS) is deployed
    Identify the device model via show version or system inventory. This vulnerability affects only CTMS, not other TelePresence products.
    Affected if The device is confirmed to be a Cisco TelePresence Multipoint Switch (CTMS)
  2. Verify Media Snapshot feature status
    Check the Media Snapshot configuration via the CTMS admin interface or CLI command (for example: show media-snapshot configuration). Determine if the feature is enabled.
    Affected if Media Snapshot feature is enabled on the device
  3. Check if user authentication is configured
    Review the CTMS user authentication settings. The vulnerability requires remote authenticated users to send the malicious requests. Check for local user accounts or remote authentication (RADIUS/TACACS+) configuration.
    Affected if Remote user authentication is enabled and users can access the Media Snapshot functionality
  4. Examine device crash/reload logs
    Review system logs, crash logs, or use show crash-info for evidence of unexpected reloads. Focus on timestamps around meeting termination events.
    Affected if Device has experienced unexplained reloads or crashes occurring during or immediately after meeting termination
  5. Monitor Media Snapshot request patterns
    If logging is available, review logs for unusually high volumes of Media Snapshot requests, particularly during meeting termination periods.
    Affected if There is a high volume of Media Snapshot requests detected, especially during meeting termination

A CTMS deployment with Media Snapshot enabled, user authentication configured, and evidence of device reloads during meeting termination indicates potential exploitation of CVE-2013-5516.

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 software update addressing CVE-2013-5516. Additionally, implement rate limiting on Media Snapshot requests at the network edge and monitor for anomalous request patterns during meeting termination events.

Fix this in Telepresence Multipoint Switch 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-2013-5516 — 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-2013-5516 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