dbcve.org
Telepresence Tc SoftwareApplication · Cisco

CVE-2014-2167

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 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
The SIP implementation in Cisco TelePresence TC Software 4.x and 5.x and TE Software 4.x and 6.0 allows remote attackers to cause a denial of service (device reload) via crafted SIP packets, aka Bug ID CSCua86589.

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

The SIP (Session Initiation Protocol) implementation in Cisco TelePresence TC Software versions 4.x and 5.x and TE Software versions 4.x and 6.0 contains a vulnerability that can be triggered by specially crafted SIP packets sent to the device. Successful exploitation causes the device to reload (crash and restart), resulting in denial of service.

MitigationApply the relevant Cisco software update or patch for this vulnerability. If immediate patching is not possible, consider implementing SIP traffic filtering at network boundaries to block potentially malicious SIP packets from untrusted sources.

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 Tc SoftwareApplication
Affected:= 4.0.0= 4.0.1= 4.0.4= 4.1.1= 4.1.2= 4.2.0= 4.2.1= 4.2.2= 4.2.3= 4.2.4= 5.0.0= 5.0.1
Telepresence Te SoftwareApplication
Affected:= 4.1.0= 4.1.1= 4.1.2= 4.1.3= 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
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 checks

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

  1. Identify the TelePresence software type
    Log into the device CLI and run 'show systemunit' or check the boot image name. TC software typically runs on codecs/endpoint devices while TE software runs on older TelePresence systems.
    Affected if The device runs Cisco TelePresence TC Software or TE Software
  2. Check the installed software version
    Execute 'show version' or 'version' in the device CLI to display the current software version.
    Affected if The version matches any of these: TC 4.0.0, 4.0.1, 4.0.4, 4.1.1, 4.1.2, 4.2.0, 4.2.1, 4.2.2, 4.2.3, 4.2.4, 5.0.0, 5.0.1 or TE 4.1.0, 4.1.1, 4.1.2, 4.1.3, 6.0
  3. Verify SIP is configured
    Run 'show sip' or 'show sip status' to check if Session Initiation Protocol is enabled on the device. Also check 'show running-config' for any sip-related configuration lines.
    Affected if SIP protocol is enabled or registered on the device
  4. Check SIP listener status
    Use 'show sip registration' or 'show sip connections' to see active SIP endpoints or call control configurations.
    Affected if The device has SIP endpoints or call control configured and listening for SIP traffic

You are affected if your TelePresence device runs TC version 4.x/5.x or TE version 4.x/6.0 from the affected list AND has SIP enabled or configured to receive SIP traffic.

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

Apply the relevant Cisco software update or patch for this vulnerability. If immediate patching is not possible, consider implementing SIP traffic filtering at network boundaries to block potentially malicious SIP packets from untrusted sources.

Fix this in Telepresence Tc Software Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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