dbcve.org
Telepresence System SoftwareApplication · Cisco

CVE-2012-3074

HIGH · 8.3 CVSS v2.0 Published 2012-07-12
Fix available
A fix is available. Upgrade to after 1.9.0.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
An unspecified API on Cisco TelePresence Immersive Endpoint Devices before 1.9.1 allows remote attackers to execute arbitrary commands by leveraging certain adjacency and sending a malformed request on TCP port 61460, aka Bug ID CSCtz38382.

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

This is a command injection vulnerability in an unspecified API on Cisco TelePresence Immersive Endpoint Devices. Attackers with network adjacency to the device can send malformed requests on TCP port 61460 to achieve arbitrary command execution. The vulnerability affects versions prior to 1.9.1.

MitigationUpgrade Cisco TelePresence Immersive Endpoint Devices to firmware version 1.9.1 or later to remediate. Additionally, network segmentation and access controls may be implemented to restrict adjacency to trusted endpoints.

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.9.0.1\(3\)= 1.2.3\(1101\)= 1.3.2\(1393\)= 1.4.7\(2229\)= 1.5.1\(2082\)= 1.5.3\(2115\)= 1.5.10\(3648\)= 1.5.11\(3659\)= 1.5.12\(3701\)= 1.5.13\(3717\)= 1.6.0\(3954\)= 1.6.2\(4023\)
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 T3Hardware / appliance
Affected:all versions
Telepresence System Tx1300 47Hardware / 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 TelePresence device model
    Access the device administrative interface or use SNMP to query the device. Check the product name or model number displayed in the web UI, CLI output (show version), or SNMP OID.
    Affected if The model is one of: Cisco Telepresence System 1300 65, 3000, 3010, 3200, 3210, T3, or Tx1300 47 (all versions are affected).
  2. Determine the firmware version
    Log into the device web interface, administrative console, or CLI and retrieve the software version. Use 'show version' command via SSH/Telnet or check the System Information page in the web UI.
    Affected if The version is below 1.9.1, or specifically matches any of these vulnerable versions: 1.9.0.1(3), 1.2.3(1101), 1.3.2(1393), 1.4.7(2229), 1.5.1(2082), 1.5.3(2115), 1.5.10(3648), 1.5.11(3659), 1.5.12(3701), 1.5.13(3717), 1.6.0(3954), or 1.6.2(4023).
  3. Check network exposure to TCP port 61460
    From a system on the same network segment as the device, run 'nc -zv <device_ip> 61460' or 'nmap -p 61460 <device_ip>' to test if the port is open and reachable.
    Affected if TCP port 61460 is accessible from untrusted or adjacent network segments. The vulnerability requires attackers to have network adjacency to send malformed requests.
  4. Verify the API service is running
    Check if the TelePresence API service is active by accessing the device web service or attempting to reach common API endpoints on port 61460.
    Affected if The API service on TCP port 61460 is running and responding to requests.

The device is affected if it is a Cisco TelePresence model listed as affected and is running a firmware version below 1.9.1 (or a specific vulnerable version) with TCP port 61460 accessible from the attacker's network location.

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.9.0.1
Interim mitigation

Upgrade Cisco TelePresence Immersive Endpoint Devices to firmware version 1.9.1 or later to remediate. Additionally, network segmentation and access controls may be implemented to restrict adjacency to trusted endpoints.

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-2012-3074 — 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-2012-3074 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