Telepresence Tc SoftwareApplication · Cisco
CVE-2014-2174
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 · uneditedCisco TelePresence T, TelePresence TE, and TelePresence TC before 7.1 do not properly implement access control, which allows remote attackers to obtain root privileges by sending packets on the local network and allows physically proximate attackers to obtain root privileges via unspecified vectors, aka Bug ID CSCub67651.
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 confidenceCisco TelePresence T, TE, and TC devices before version 7.1 have improper access control that allows remote attackers on the local network to obtain root privileges by sending packets, and allows physically proximate attackers to obtain root privileges via unspecified vectors.
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
= 3.1.5= 3.1_base= 4.1.0= 4.1.1= 4.1.2= 4.1_base= 4.2.0= 4.2.1= 4.2.2= 4.2.3= 4.2.4= 4.2_base
Telepresence Te SoftwareApplication
= 6.0.0= 6.0.1= 6.0.2= 6.0_baseCVSS 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
- Adjacent
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:A/AC:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Cisco TelePresence device modelCheck the device label, web interface, or CLI output for the exact model (T, TE, or TC series)Affected if Device is a Cisco TelePresence T, TE, or TC series unit
-
Determine the installed software versionAccess the device web interface under 'System Information' or use the CLI command 'show version' to retrieve the TC or TE software version numberAffected if Version is 3.1.5, 3.1_base, 4.1.0, 4.1.1, 4.1.2, 4.1_base, 4.2.0, 4.2.1, 4.2.2, 4.2.3, 4.2.4, 4.2_base (for TC) or 6.0.0, 6.0.1, 6.0.2, 6.0_base (for TE)
-
Verify the version is below 7.1Compare the installed version number to 7.1; versions 7.1 and later are patchedAffected if Installed version is less than 7.1 (e.g., 6.x, 4.x, 3.x)
-
Confirm network accessibility of the deviceVerify the device has an active IP address and is reachable on the local network; the vulnerability is exploitable by remote attackers on the same local networkAffected if Device is network-accessible and no network segmentation isolates it from untrusted hosts
The device is affected if it is a Cisco TelePresence T, TE, or TC running software version 7.0 or earlier, particularly when the device is accessible on a network where untrusted hosts can send packets to it.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade Cisco TelePresence devices to version 7.1 or later to remediate this access control vulnerability that allows privilege escalation to root.
Fix this in Telepresence Tc Software
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2174 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-2174 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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