dbcve.org
Telepresence Video Communication ServerApplication · Cisco

CVE-2016-1400

HIGH · 7.5 CVSS v3.0 Published 2016-05-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/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 Communications Server (VCS) X8.x before X8.7.2 allows remote attackers to cause a denial of service (service disruption) via a crafted URI in a SIP header, aka Bug ID CSCuy43258.

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 Communications Server (VCS) versions X8.x before X8.7.2 contains a denial of service vulnerability where remote attackers can send specially crafted SIP requests containing malicious URIs in SIP headers, causing the service to become unresponsive or crash.

MitigationUpgrade Cisco VCS to version X8.7.2 or later. Until the upgrade can be performed, consider implementing SIP traffic filtering, rate limiting, or IP-based access controls at the network perimeter to reduce exposure 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 Video Communication ServerApplication
Affected:= x8.1.1= x8.1.2= x8.1_base= x8.2.1= x8.2.2= x8.2_base= x8.5= x8.5.0= x8.5.1= x8.5.2= x8.5.3= x8.6.0

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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 Cisco VCS version
    Log into the VCS admin interface and navigate to System > System Statistics, or run 'xstatus version' via CLI. Alternatively, check the welcome page of the web interface which displays the current software version.
    Affected if The installed version matches one of: x8.1.1, x8.1.2, x8.1_base, x8.2.1, x8.2.2, x8.2_base, x8.5, x8.5.0, x8.5.1, x8.5.2, x8.5.3, x8.6.0, or any X8.x version prior to X8.7.2.
  2. Verify if SIP is enabled on the VCS
    In the VCS admin interface, go to Configuration > SIP > Configuration. Confirm whether SIP mode is enabled or if SIP protocols are active. From CLI, use 'sip status' to check the SIP service state.
    Affected if SIP is enabled and the device is running an affected version.
  3. Check SIP listener binding and ports
    Navigate to Configuration > Protocols > SIP > SIP page in the admin interface, or run 'sip listen' via CLI. Identify which interfaces/IPs the SIP service is bound to (typically ports 5060 for UDP/TCP and 5061 for TLS).
    Affected if The SIP service is bound to any interface and the version is affected.
  4. Assess network exposure of SIP ports
    Review firewall rules or network accessibility of the VCS IP address on ports 5060 and 5061. From an external host, verify if these ports are reachable (e.g., nmap -p 5060,5061 <VCS_IP>). Check if the VCS is directly accessible from untrusted networks.
    Affected if SIP ports are exposed to untrusted or public networks and the version is affected.

You are affected if your Cisco VCS runs any version from x8.1.1 through x8.6.0 (or any X8.x version below X8.7.2) and has SIP enabled and exposed to the network.

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 to version X8.7.2 or later. Until the upgrade can be performed, consider implementing SIP traffic filtering, rate limiting, or IP-based access controls at the network perimeter to reduce exposure to untrusted networks.

Fix this in Telepresence Video Communication Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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