dbcve.org
Telepresence Te SoftwareApplication · Cisco

CVE-2014-2165

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 CSCtq72699.

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 · moderate confidence

The SIP implementation in Cisco TelePresence TC Software (4.x, 5.x) and TE Software (4.x, 6.0) contains a parsing vulnerability that allows remote attackers to trigger a device reload via crafted SIP packets. The flaw allows malformed SIP traffic to cause a denial of service condition.

MitigationApply the Cisco patch for CSCtq72699 when available. At the network perimeter, implement SIP traffic filtering, validation, and rate limiting to block malformed packets before they reach affected devices.

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 Te SoftwareApplication
Affected:= 4.1.0= 4.1.1= 4.1.2= 4.1.3= 6.0
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

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 device type
    Access the Cisco TelePresence device CLI or admin web interface and run 'show device' or check the system information page to confirm the device model (TC or TE series)
    Affected if The device is not a Cisco TelePresence TC or TE series endpoint
  2. Check the software version
    Run 'show version' in the CLI or check the software version in the admin interface under System > Software
    Affected if The installed version matches 4.1.0, 4.1.1, 4.1.2, 4.1.3, or 6.0 for TE software, or 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, or 5.0.1 for TC software
  3. Verify SIP is enabled
    Check the device configuration via CLI with 'show sip' or in the admin interface under Protocols > SIP to see if SIP signaling is configured and enabled
    Affected if SIP protocol is enabled and configured on the device (the vulnerability only affects devices using SIP)
  4. Check SIP network exposure
    Review the network configuration to determine if the device's SIP port (typically 5060) is exposed to untrusted networks by checking firewall rules or NAT configuration
    Affected if The SIP interface is reachable from outside the trusted network without filtering

The device is affected if it is a Cisco TelePresence TC or TE device running one of the listed versions AND has SIP enabled and exposed to network 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 Cisco patch for CSCtq72699 when available. At the network perimeter, implement SIP traffic filtering, validation, and rate limiting to block malformed packets before they reach affected devices.

Fix this in Telepresence Te Software Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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