dbcve.org
Telepresence Multipoint Switch SoftwareApplication · Cisco

CVE-2012-3073

HIGH · 7.8 CVSS v2.0 Published 2012-07-12
Fix available
A fix is available. Upgrade to after 1.9.0.1 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable 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 IP implementation on Cisco TelePresence Multipoint Switch before 1.8.1, Cisco TelePresence Manager before 1.9.0, and Cisco TelePresence Recording Server 1.8 and earlier allows remote attackers to cause a denial of service (networking outage or process crash) via (1) malformed IP packets, (2) a high rate of TCP connection requests, or (3) a high rate of TCP connection terminations, aka Bug IDs CSCti21830, CSCti21851, CSCtj19100, CSCtj19086, CSCtj19078, CSCty11219, CSCty11299, CSCty11323, and CSCty11338.

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 · moderate confidence

Multiple Cisco TelePresence products (Multipoint Switch before 1.8.1, Manager before 1.9.0, Recording Server 1.8 and earlier) contain IP implementation flaws allowing remote attackers to trigger denial of service via malformed IP packets, rapid TCP connection requests, or rapid TCP connection terminations. This causes networking outages or process crashes.

MitigationUpgrade affected Cisco TelePresence products to version 1.8.1 or later for Multipoint Switch, 1.9.0 or later for Manager, and the latest available version for Recording Server. Consider network segmentation and rate limiting as compensating controls until patching is completed.

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 Multipoint Switch SoftwareApplication
Affected:<= 1.8.0\(1026\)= 1.0.4.0= 1.0.4.0\(21\)= 1.1.0= 1.1.0\(254\)= 1.1.1= 1.1.1\(30\)= 1.1.2= 1.1.2\(6\)= 1.5.0= 1.5.0\(222\)= 1.5.1
Telepresence Multipoint SwitchHardware / appliance
Affected:all versions
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

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
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 checks

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

  1. Identify Cisco TelePresence product type
    Run 'show version' or check system documentation to confirm the exact Cisco TelePresence product model (Multipoint Switch, System 1300, 3000, 3010, 3200, or 3210)
    Affected if The device is any of the Cisco TelePresence models listed in the CVE (Multipoint Switch, System 1300, 3000, 3010, 3200, 3210)
  2. Determine Multipoint Switch Software version
    Run 'show version' or access the admin interface to retrieve the software version number for Multipoint Switch Software
    Affected if Version is 1.8.0(1026) or earlier, or matches any specific version listed (1.0.4.0, 1.0.4.0(21), 1.1.0, 1.1.0(254), 1.1.1, 1.1.1(30), 1.1.2, 1.1.2(6), 1.5.0, 1.5.0(222), or 1.5.1)
  3. Determine TelePresence System Software version
    Run 'show version' or check the system software version through the management interface
    Affected if Version is 1.9.0.1(3) or earlier, or matches any specific version listed (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))
  4. Confirm hardware appliance model
    Check the physical device model number or run 'show hardware' to identify if it is a Telepresence System 1300 65, 3000, 3010, 3200, or 3210 appliance
    Affected if The device is a Cisco Telepresence System 1300 65, 3000, 3010, 3200, or 3210 (these have all versions affected)
  5. Verify IP network exposure
    Check network configuration and firewall rules to determine if the TelePresence management or signaling ports are exposed to untrusted networks
    Affected if The device IP interfaces are reachable from networks where malicious actors could send malformed IP packets or rapid TCP connection requests

The environment is affected if any Cisco TelePresence product matches the specific version ranges listed or is a System 1300/3000/3010/3200/3210 model, and the device network interfaces are accessible to potential attackers.

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 affected Cisco TelePresence products to version 1.8.1 or later for Multipoint Switch, 1.9.0 or later for Manager, and the latest available version for Recording Server. Consider network segmentation and rate limiting as compensating controls until patching is completed.

Fix this in Telepresence Multipoint Switch Software Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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