dbcve.org
Telepresence Te SoftwareApplication · Cisco

CVE-2014-2168

HIGH · 7.6 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 →
85/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
Buffer overflow in Cisco TelePresence TC Software 4.x and 5.x and TE Software 4.x and 6.0 allows remote attackers to execute arbitrary code via crafted DNS response packets, aka Bug ID CSCty44804.

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

Buffer overflow in Cisco TelePresence TC Software (4.x, 5.x) and TE Software (4.x, 6.0) allows remote unauthenticated attackers to execute arbitrary code via specially crafted DNS response packets that overflow a fixed-size buffer during DNS processing.

MitigationApply Cisco-provided security patches for the affected software versions; consider network segmentation and firewall rules to restrict DNS traffic to trusted sources as a compensating control.

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

AV:N/AC:H/Au:N/C:C/I:C/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 product
    Access the system admin interface or use CLI command 'show version' to determine if the device runs TC Software or TE Software
    Affected if The device runs Cisco TelePresence TC Software version 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 Software version 4.1.0, 4.1.1, 4.1.2, 4.1.3, 6.0
  2. Confirm the exact software version
    Run the CLI command 'show version' or check the system administration page to retrieve the precise software version number
    Affected if The installed version matches exactly one of the following: 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; TE: 4.1.0, 4.1.1, 4.1.2, 4.1.3, 6.0
  3. Verify DNS functionality is enabled
    Check the system network settings through the admin interface or run CLI command 'show network dns' to see if DNS resolution is configured and active
    Affected if DNS is configured and the system is capable of processing DNS responses
  4. Check network exposure to untrusted DNS
    Review firewall rules and network segmentation to determine if the TelePresence device can receive DNS responses from untrusted or external network sources
    Affected if The device can receive DNS responses from networks outside the trusted internal network

A system is affected by CVE-2014-2168 when it runs a matching TC or TE version listed above and has DNS processing enabled, with network exposure to potentially malicious DNS responses.

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 Cisco-provided security patches for the affected software versions; consider network segmentation and firewall rules to restrict DNS traffic to trusted sources as a compensating control.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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