dbcve.org
Telepresence Tc SoftwareApplication · Cisco

CVE-2014-2175

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
Cisco TelePresence TC Software 4.x and 5.x and TE Software 4.x and 6.0 allow remote attackers to cause a denial of service (memory consumption) via crafted H.225 packets, aka Bug ID CSCtq78849.

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 TC Software (versions 4.x and 5.x) and TE Software (versions 4.x and 6.0) contains a memory consumption vulnerability in the H.225 call signaling protocol handler. Remote attackers can send specially crafted H.225 packets to cause excessive memory allocation, leading to denial of service.

MitigationApply vendor patches from Cisco when available. In the interim, implement network-level filtering or rate limiting for H.225 traffic at perimeter firewalls to block malicious packets.

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 Cisco TelePresence software type and version
    Access the device administrative interface or CLI and run 'show version' or check system information to determine if TC or TE software is installed and note the exact version number
    Affected if The installed version matches one of: 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
  2. Confirm H.225 call signaling is enabled
    Check the device configuration for H.225 protocol settings, typically found in the VoIP or call signaling configuration section of the TelePresence admin interface
    Affected if H.225 call signaling protocol handling is enabled and the device is configured to accept H.225 connections
  3. Verify network exposure to H.225 traffic
    Review firewall rules and network segmentation to determine if the TelePresence device is directly accessible from untrusted networks on ports used for H.225 signaling (typically port 1720)
    Affected if The device has open inbound access from untrusted networks on H.225 signaling ports and is reachable by potential remote attackers

The environment is affected if running a matching TC or TE version with H.225 enabled and network exposure to untrusted sources.

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 vendor patches from Cisco when available. In the interim, implement network-level filtering or rate limiting for H.225 traffic at perimeter firewalls to block malicious packets.

Fix this in Telepresence Tc Software Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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