Telepresence System SoftwareApplication · Cisco

CVE-2014-2159

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

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 CSCtq78722.

Technical summary

dbcve analysis · high confidence

Denial of service vulnerability in the H.225 signaling protocol subsystem of Cisco TelePresence System MXP Series devices. Remote attackers can send crafted H.225 packets to trigger an uncontrolled reload of the device, causing service disruption.

MitigationUpgrade Cisco TelePresence MXP Series Software to version F9.3.1 or later to patch the vulnerability in the H.225 subsystem.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

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

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify the device model

Run 'show system' or 'show version' command on the Cisco TelePresence device to confirm it is an MXP Series device (2000 Mxp, 550 Mxp, 770 Mxp, 880 Mxp, 990 Mxp, 1000 Mxp, or 1700 Mxp)

Affected if The device is any Cisco Tandberg MXP or Cisco Telepresence System MXP model
Check the installed software version

Execute 'show version' or 'show software' command to retrieve the current firmware version installed on the device

Affected if The software version is <= f9.3, or exactly 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
Verify H.225 protocol subsystem is active

Check the device signaling configuration via 'show call control' or 'show h225' command to determine if H.225 (part of H.323 protocol stack) is enabled and used for VoIP/telepresence calls

Affected if H.225 signaling protocol is enabled and the device accepts H.323-based calls
Confirm H.323 gateway configuration

Inspect 'show gateway' or 'show h323' configuration to see if the device is configured as an H.323 gateway or endpoint accepting H.225 signaling

Affected if The device is configured as an H.323 gateway or endpoint accepting incoming H.225 signaling connections

The device is affected if it is a Cisco TelePresence MXP Series device running software version f9.3 or earlier (or any of the specific listed versions) with H.225 signaling protocol enabled.

Generated from the published advisory. Verify against your own configuration.

Remediation

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 patch the vulnerability in the H.225 subsystem.

Fix this in Telepresence System Software Scoped from the published advisory

Consultation2.0 h
Implementation4.0 h
Testing2.0 h
Review / QA1.0 h

9.0 hours of engineering $1,600

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

tools.cisco.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-2159 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2014-2159?

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.

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

At a glance

A fix existsA vendor remedy is published

Severity 7.8 High

Exploit likelihood EPSS, next 30 days 1.6%

Affects: Telepresence System Software

Remediation

A high-priority fix

Fix this in Telepresence System Software 9 hrs · Moderate

Typical engagement from $1,600

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2014-2159 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References