dbcve.org
Telepresence System SoftwareApplication · Cisco

CVE-2014-2160

HIGH · 7.8 CVSS v2.0 Published 2014-05-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/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
The H.225 subsystem in Cisco TelePresence System MXP Series Software before F9.3.1 allows remote attackers to cause a denial of service (device reload) via crafted packets, aka Bug ID CSCty45745.

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

This is a denial of service vulnerability in the H.225 signaling subsystem of Cisco TelePresence System MXP Series devices. Remote attackers can send specially crafted H.225 protocol packets to trigger an uncontrolled reload (reboot) of the device, causing service disruption.

MitigationUpgrade Cisco TelePresence MXP Series Software to version F9.3.1 or later to remediate this vulnerability. If immediate patching is not possible, consider network segmentation to limit exposure of TelePresence devices to untrusted networks.

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 System SoftwareApplication
Affected:<= f9.3= f9.0.1= f9.0.2= f9.1.0= f9.1.1= f9.1.2= fnc9.1.0= fnc9.1.1= fnc9.1.2= fnc9.3
Tandberg 2000 MxpHardware / appliance
Affected:all versions
Tandberg 550 MxpHardware / appliance
Affected:all versions
Tandberg 770 MxpHardware / appliance
Affected:all versions
Tandberg 880 MxpHardware / appliance
Affected:all versions
Tandberg 990 MxpHardware / appliance
Affected:all versions
Telepresence System 1000 MxpHardware / appliance
Affected:all versions
Telepresence System 1700 MxpHardware / 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
Low
Authentication
None
Confidentiality
None
Integrity
None
Availability
Complete

AV:N/AC:L/Au:N/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. Identify the device model
    Log into the Cisco TelePresence device or check the device inventory to confirm the exact model name (e.g., Cisco Tandberg 550 Mxp, Cisco Telepresence System 1000 Mxp, etc.)
    Affected if The device is any Tandberg MXP model (2000, 550, 770, 880, 990) or Cisco Telepresence System 1000/1700 Mxp, as these are affected in all versions
  2. Check the software version
    Access the device admin interface or use the command line (typically 'show version' or through the web interface under 'System Information') to retrieve the installed software version
    Affected if The software version is f9.3 or lower, or specifically f9.0.1, f9.0.2, f9.1.0, f9.1.1, f9.1.2, fnc9.1.0, fnc9.1.1, fnc9.1.2, or fnc9.3 (these are the explicitly affected versions)
  3. Verify H.225 signaling is enabled
    Check the device configuration settings for H.225 protocol settings. This is typically found in the VoIP/H.323 or signaling configuration section of the device web interface or CLI (commands like 'show running-config' or checking 'H.323' or 'SIP' settings)
    Affected if H.225 signaling is enabled and the device is accepting H.225 connections, as this is the attack surface for the vulnerability
  4. Confirm the device is network accessible
    Verify that the TelePresence device has an IP address and is reachable on the network, particularly on ports used for H.225 signaling (typically port 1720 for H.323 call setup)
    Affected if The device is accessible on the network and can receive external H.225 packets, which is required for remote exploitation

The environment is affected if the device is a Cisco TelePresence MXP or Tandberg MXP series with software version f9.3 or earlier (or the specific versions listed), and H.225 signaling is enabled and network-accessible.

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

Upgrade Cisco TelePresence MXP Series Software to version F9.3.1 or later to remediate this vulnerability. If immediate patching is not possible, consider network segmentation to limit exposure of TelePresence devices to untrusted networks.

Fix this in Telepresence System Software Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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