dbcve.org
Telepresence Video Communication Server SoftwareApplication · Cisco

CVE-2014-3370

HIGH · 7.1 CVSS v2.0 Published 2014-10-19
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 Video Communication Server (VCS) and Expressway Software before X8.1.1 allow remote attackers to cause a denial of service (device reload) via crafted SIP packets, aka Bug IDs CSCum60442 and CSCum60447.

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

Cisco TelePresence Video Communication Server (VCS) and Expressway Software versions before X8.1.1 contain a vulnerability in SIP packet handling that allows remote unauthenticated attackers to send specially crafted SIP packets causing the device to reload, resulting in denial of service.

MitigationUpgrade Cisco VCS and Expressway software to version X8.1.1 or later to remediate this vulnerability. Implement SIP traffic filtering at network boundaries as a compensating control if immediate upgrade is not feasible.

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 Video Communication Server SoftwareApplication
Affected:<= x8.1
Expressway SoftwareApplication
Affected:<= x8.1

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 installed product
    Log into the Cisco TelePresence device and check the product name in the system information or run 'xstatus' command to confirm whether it is a VCS (Video Communication Server) or Expressway appliance
    Affected if The device is a Cisco TelePresence VCS or Expressway system
  2. Check the software version
    Run the command 'version' or check the system information page in the web interface to retrieve the installed software version number
    Affected if The version is x8.1 or earlier (for example, x8.0, x7.x, etc.)
  3. Verify SIP is enabled
    Check the SIP configuration in the device web interface under 'Configuration > Protocols > SIP' or run 'xconfiguration SIP' command to see if SIP is turned on
    Affected if SIP protocol is enabled and the device is reachable over the network with SIP traffic permitted

The environment is affected if the device runs Cisco VCS or Expressway software version x8.1 or earlier and has SIP protocol enabled, allowing specially crafted SIP packets to trigger a denial of service condition.

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 VCS and Expressway software to version X8.1.1 or later to remediate this vulnerability. Implement SIP traffic filtering at network boundaries as a compensating control if immediate upgrade is not feasible.

Fix this in Telepresence Video Communication Server Software Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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