dbcve.org
Telepresence System SoftwareApplication · Cisco

CVE-2014-2157

HIGH · 7.1 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 →
80/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
Cisco TelePresence System MXP Series Software before F9.3.1 allows remote attackers to cause a denial of service (device reload) via crafted SIP packets, aka Bug ID CSCty45733.

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 Cisco TelePresence System MXP Series devices running software versions prior to F9.3.1. Attackers can send specially crafted SIP (Session Initiation Protocol) packets to the affected device, causing it to reload unexpectedly and become unavailable.

MitigationUpgrade Cisco TelePresence MXP Series Software to version F9.3.1 or later to remediate this vulnerability. Consider implementing network-level SIP traffic filtering or rate limiting at perimeter devices to reduce attack surface until the upgrade can be performed.

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

AV:N/AC:M/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
    Access the device CLI or web interface and retrieve the hardware model name. Look for model identifiers such as Tandberg 2000 MXP, Tandberg 550 MXP, Tandberg 770 MXP, Tandberg 880 MXP, Tandberg 990 MXP, Cisco TelePresence System 1000 MXP, or Cisco TelePresence System 1700 MXP.
    Affected if The device is any of the Tandberg MXP or Cisco TelePresence System MXP models listed in the affected products.
  2. Check the software version
    In the device CLI, run the command 'show version' or 'xversion' to display the running software version. Alternatively, access the web interface and navigate to the system information or status page.
    Affected if The version is F9.3.0 or lower, or matches any of these specific versions: 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.
  3. Confirm SIP is enabled
    In the device CLI, run 'show sip' or 'show registration' to check if SIP protocol is configured and enabled. Also check the configuration with 'show run | include sip'. In the web interface, look under VoIP or SIP settings.
    Affected if SIP is enabled and the device is reachable on the network for SIP traffic.
  4. Verify network exposure
    Check if the device has an accessible IP address and whether SIP ports (typically 5060/5061 UDP/TCP) are open to untrusted networks. Review firewall rules or access control lists protecting the device.
    Affected if The device SIP interface is exposed to external or untrusted networks without filtering.

If the device is a Cisco TelePresence MXP Series or Tandberg MXP model running software version lower than F9.3.1 and has SIP enabled and reachable, the environment is affected by this CVE.

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. Consider implementing network-level SIP traffic filtering or rate limiting at perimeter devices to reduce attack surface until the upgrade can be performed.

Fix this in Telepresence System Software Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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