Telepresence System SoftwareApplication · Cisco
CVE-2014-2161
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 · uneditedThe 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 CSCty45731.
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 confidenceA denial of service vulnerability exists in the H.225 subsystem of Cisco TelePresence System MXP Series Software prior to version F9.3.1. Remote attackers can send specially crafted H.225 packets to trigger an uncontrolled reload of the device, causing service disruption.
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
<= 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
all versions
Tandberg 550 MxpHardware / appliance
all versions
Tandberg 770 MxpHardware / appliance
all versions
Tandberg 880 MxpHardware / appliance
all versions
Tandberg 990 MxpHardware / appliance
all versions
Telepresence System 1000 MxpHardware / appliance
all versions
Telepresence System 1700 MxpHardware / appliance
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Cisco TelePresence device modelAccess the device admin interface or use the 'show version' command via CLI to determine the exact model (e.g., Tandberg 2000 Mxp, Tandberg 550 Mxp, Telepresence System 1000 Mxp, etc.)Affected if The device is a Cisco Tandberg MXP series (2000, 550, 770, 880, 990) or Telepresence System MXP (1000, 1700) - all versions of these are affected
-
Check the software versionUse the 'show version' command or access the device web interface to view the installed software versionAffected if The version is f9.3 or earlier, 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 (versions prior to F9.3.1)
-
Verify H.225 protocol is enabledCheck the device configuration for H.225 settings. This is typically found in the VoIP or call signaling configuration section of the device admin interface, or via 'show running-config' looking for H.225 related entriesAffected if H.225 signaling is enabled and the device accepts H.225 packets from the network
You are affected if your device is a Cisco Tandberg MXP series or Telepresence System MXP with software version earlier than F9.3.1, and H.225 protocol is enabled for call signaling.
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 dataUpgrade Cisco TelePresence System MXP Series Software to version F9.3.1 or later. If immediate upgrade is not feasible, restrict network access to the telepresence devices by placing them behind firewalls or in isolated network segments to reduce exposure 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
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 locallyCheck whether your project pulls in CVE-2014-2161 — 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-2014-2161 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