Telepresence System SoftwareApplication · Cisco

CVE-2013-1246

MEDIUM · 6.8 CVSS v2.0 Published 2013-05-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable 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 System Software does not properly handle inactive t-shell sessions, which allows remote authenticated users to cause a denial of service (memory consumption and service outage) by establishing multiple SSH connections, aka Bug ID CSCug77610.

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 System Software fails to properly handle inactive t-shell (telnet shell) sessions initiated over SSH connections. When authenticated users establish multiple SSH connections and leave them idle, the software does not release the associated memory resources, leading to progressive memory consumption that eventually causes a denial of service.

MitigationImplement SSH connection limits and session idle timeouts on the TelePresence system to prevent accumulation of inactive sessions; monitor memory usage; apply Cisco patches when available.

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 System SoftwareApplication
Affected:all versions

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

AV:N/AC:L/Au:S/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 system product
    Log into the device and run 'show version' or 'show system information' to confirm the device is running Cisco TelePresence System Software
    Affected if The device is a Cisco TelePresence System running any version of the software
  2. Check for idle SSH sessions
    Use 'show users' or 'show ssh sessions' command to list all active SSH connections and identify sessions that appear idle or have been connected for extended periods without activity
    Affected if Multiple SSH sessions are present and remain in an idle state for prolonged periods
  3. Monitor memory consumption
    Run 'show memory' or 'show processes memory' periodically over time to observe if available memory is progressively decreasing
    Affected if Free memory steadily decreases over time, especially when idle SSH sessions are present
  4. Review session configuration
    Check the SSH daemon configuration for session timeout settings using 'show running-config | include ssh' or similar command to see if session idle timeouts are defined
    Affected if No session idle timeout is configured, allowing sessions to remain open indefinitely
  5. Count accumulated t-shell processes
    Use 'show processes' or 'show system processes' to enumerate t-shell or telnet shell processes and compare count against active user sessions
    Affected if The number of t-shell processes exceeds the number of actively used sessions, indicating leaked processes

A Cisco TelePresence System is affected if it has idle SSH/t-shell sessions that are not being terminated and memory usage is growing proportionally to session count.

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

Implement SSH connection limits and session idle timeouts on the TelePresence system to prevent accumulation of inactive sessions; monitor memory usage; apply Cisco patches when available.

Fix this in Telepresence System Software Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-1246 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-1246 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