dbcve.org
Telepresence System SoftwareApplication · Cisco

CVE-2014-0661

HIGH · 8.3 CVSS v2.0 Published 2014-01-22
Fix available
A fix is available. Upgrade to after 1.10.1 or later.
See remediation →
88/100
Remediation priority · High
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
The System Status Collection Daemon (SSCD) in Cisco TelePresence System 500-37, 1000, 1300-65, and 3xxx before 1.10.2(42), and 500-32, 1300-47, TX1310 65, and TX9xxx before 6.0.4(11), allows remote attackers to execute arbitrary commands or cause a denial of service (stack memory corruption) via a crafted XML-RPC message, aka Bug ID CSCui32796.

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

The System Status Collection Daemon (SSCD) in Cisco TelePresence systems fails to properly validate XML-RPC messages, allowing remote attackers to inject arbitrary commands or cause stack memory corruption leading to denial of service. This is a pre-authentication vulnerability in a network-facing service.

MitigationApply vendor-supplied patches (1.10.2(42) for 3xxx series, 6.0.4(11) for TX series). If patching is not immediately feasible, restrict network access to the SSCD service via firewall rules or network segmentation to limit exposure.

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:<= 1.10.1\(43\)= 1.5.10\(3648\)= 1.7.5\(42\)= 1.7.6\(4\)= 1.8.0\(55\)= 1.8.1\(34\)= 1.8.2\(11\)= 1.8.3\(4\)= 1.8.4\(13\)= 1.8.5\(4\)= 1.9.0\(46\)= 1.9.1\(68\)
Telepresence System 1000Hardware / appliance
Affected:all versions
Telepresence System 1300 65Hardware / appliance
Affected:all versions
Telepresence System 3000Hardware / appliance
Affected:all versions
Telepresence System 3010Hardware / appliance
Affected:all versions
Telepresence System 3200Hardware / appliance
Affected:all versions
Telepresence System 3210Hardware / appliance
Affected:all versions
Telepresence System 500 37Hardware / appliance
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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Cisco TelePresence system model
    Access the system admin interface or use CLI commands such as 'show version' or 'show system information' to determine the exact TelePresence system model (e.g., System 1000, 1300, 3000, 3010, 3200, 3210, or 500)
    Affected if The system model matches any of the following: System 1000, System 1300 65, System 3000, System 3010, System 3200, System 3210, or System 500 37 - these are affected in all versions
  2. Check the TelePresence System Software version
    Use the admin interface or CLI command 'show version' to obtain the installed software version number
    Affected if The version is 1.10.1(43) or earlier, or exactly matches any of these: 1.5.10(3648), 1.7.5(42), 1.7.6(4), 1.8.0(55), 1.8.1(34), 1.8.2(11), 1.8.3(4), 1.8.4(13), 1.8.5(4), 1.9.0(46), or 1.9.1(68)
  3. Verify the SSCD service is running and exposed
    Check if the System Status Collection Daemon (SSCD) is enabled and listening on the network. Consult system documentation or use network scanning to identify open ports associated with SSCD (typically XML-RPC on port 8080 or similar)
    Affected if SSCD is running and accessible on a network-facing interface without firewall protection

Your environment is affected if you run any Cisco TelePresence System 1000, 1300, 3000, 3010, 3200, 3210, or 500 (all versions), or if your TelePresence System Software version matches the specific versions listed (1.10.1(43) or earlier, or any of the exact versions 1.5.10 through 1.9.1 listed), and the SSCD service is network-accessible.

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
Upgrade available Upgrade to a release after 1.10.1
Interim mitigation

Apply vendor-supplied patches (1.10.2(42) for 3xxx series, 6.0.4(11) for TX series). If patching is not immediately feasible, restrict network access to the SSCD service via firewall rules or network segmentation to limit exposure.

Fix this in Telepresence System Software Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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