dbcve.org
Telepresence System SoftwareApplication · Cisco

CVE-2012-3075

HIGH · 9.0 CVSS v2.0 Published 2012-07-12
Fix available
A fix is available. Upgrade to after 1.7.2 or later.
See remediation →
96/100
Remediation priority · Urgent
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
The administrative web interface on Cisco TelePresence Immersive Endpoint Devices before 1.7.4 allows remote authenticated users to execute arbitrary commands via a malformed request on TCP port 443, aka Bug ID CSCtn99724.

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

Command injection vulnerability in the administrative web interface of Cisco TelePresence Immersive Endpoint Devices. Authenticated remote users can execute arbitrary operating system commands via malformed requests on TCP port 443 (HTTPS). Affected versions are before firmware version 1.7.4.

MitigationUpgrade Cisco TelePresence Immersive Endpoint Devices to firmware version 1.7.4 or later. Until upgrade is possible, restrict network access to the administrative interface on port 443 to trusted IPs only and monitor for suspicious authenticated activity.

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.7.2\(4937\)= 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
Network
Complexity
Low
Authentication
Single
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:S/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 device model
    Access the administrative web interface or check the device label/system information to confirm the exact model (System 1300, 3000, 3010, 3200, 3210, T3, Tx1300 47, or determine if running Telepresence System Software)
    Affected if The model matches any of the affected products listed in the CVE (System 1300 65, 3000, 3010, 3200, 3210, T3, or Tx1300 47)
  2. Determine the firmware version
    Log into the administrative web interface and navigate to System or Status pages to view the firmware version, or use the CLI command 'show version' if available
    Affected if The firmware version is below 1.7.4, or matches any of the specific affected versions listed (1.2.3, 1.3.2, 1.4.7, 1.5.1, 1.5.3, 1.5.10, 1.5.11, 1.5.12, 1.5.13, 1.6.0, 1.6.2, or any version <= 1.7.2)
  3. Confirm the administrative web interface is accessible on port 443
    Attempt to reach the device HTTPS interface by navigating to https://<device-ip>/ on TCP port 443, or verify port 443 is listening with a network scanner
    Affected if The HTTPS administrative interface on port 443 is exposed and accessible
  4. Verify authentication is enabled for the web interface
    Check that the administrative web interface requires valid credentials for access (default admin account or configured user accounts)
    Affected if The web interface accepts authentication credentials, which is required for exploiting this vulnerability

The device is affected if it is a Cisco TelePresence model listed in the CVE, runs firmware version 1.7.3 or below, and has the administrative web interface on port 443 accessible with authentication enabled.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 1.7.2
Interim mitigation

Upgrade Cisco TelePresence Immersive Endpoint Devices to firmware version 1.7.4 or later. Until upgrade is possible, restrict network access to the administrative interface on port 443 to trusted IPs only and monitor for suspicious authenticated activity.

Recommended fix High confidence

Telepresence System Software version 1.7.4 or later

  1. 1. Identify the specific Cisco TelePresence device model in your environment
  2. 2. Access the device's web interface or CLI to determine the current software version
  3. 3. Navigate to Cisco's software download page and download version 1.7.4 or later for your specific device model
  4. 4. Back up the current device configuration
  5. 5. Upload the new firmware image through the administrative web interface or via TFTP/FTP depending on device capabilities
  6. 6. Reboot the device to apply the new firmware
  7. 7. Verify the device is running version 1.7.4 or later by checking the system information
  8. 8. Confirm the administrative web interface on TCP port 443 is now patched
Caveat Review Cisco release notes for version 1.7.4 to check for any configuration or feature changes that may affect your deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Telepresence System Software Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,150
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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