Telepresence Tc SoftwareApplication · Cisco
CVE-2015-0722
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 · uneditedThe network drivers in Cisco TelePresence T, Cisco TelePresence TE, and Cisco TelePresence TC before 7.3.2 allow remote attackers to cause a denial of service (process restart or device reload) via a flood of crafted IP packets, aka Bug ID CSCuj68952.
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 confidenceA vulnerability in the network driver code of Cisco TelePresence T, TE, and TC devices allows remote attackers to send crafted IP packets that cause the device to reload or restart specific processes, resulting in denial of service. The vulnerability is triggered by packet floods with malformed IP headers.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify device modelRun 'show system info' or access the device admin interface to confirm the exact model number is Cisco TelePresence T, TE, or TC seriesAffected if Model is TelePresence T, TE, or TC series (any variant)
-
Check installed software versionRun 'show version' or 'show software' command to retrieve the current firmware/software version installed on the deviceAffected if Version matches any of these: Tc: 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; Te: 6.0.0, 6.0.1, 6.0.2, 6.0_base
-
Verify network interfaces are configuredRun 'show ip interface' or check the device network configuration to confirm IP interfaces are enabledAffected if Device has IP interfaces configured and operational (network stack is active)
-
Check network exposureReview network topology and firewall rules to determine if the device is directly reachable from untrusted networks or the internetAffected if Device is directly accessible from WAN or untrusted networks without intermediate filtering
Device is affected if it is a Cisco TelePresence T, TE, or TC running any of the listed affected versions AND has active IP network interfaces that could receive malformed packets from an attacker.
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 TC, TE, and T firmware to version 7.3.2 or later to patch the vulnerable network driver code.
Fix this in Telepresence Tc Software
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0722 — 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-2015-0722 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