CVE-2012-2486
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 · uneditedThe Cisco Discovery Protocol (CDP) implementation on Cisco TelePresence Multipoint Switch before 1.9.0, Cisco TelePresence Immersive Endpoint Devices before 1.9.1, Cisco TelePresence Manager before 1.9.0, and Cisco TelePresence Recording Server before 1.8.1 allows remote attackers to execute arbitrary code by leveraging certain adjacency and sending a malformed CDP packet, aka Bug IDs CSCtz40953, CSCtz40947, CSCtz40965, and CSCtz40953.
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 confidenceA remote code execution vulnerability exists in the Cisco Discovery Protocol (CDP) implementation on multiple Cisco TelePresence products (Multipoint Switch, Immersive Endpoint Devices, Manager, and Recording Server). Attackers who have adjacency to the affected device can exploit this by sending a malformed CDP packet, allowing execution of arbitrary code with elevated privileges.
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<= 1.8.3\(9\)= 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.1all 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\)= 1.6.2\(4023\)all versionsall versionsall versionsall versionsall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the TelePresence product typeDetermine which Cisco TelePresence product is running. Common commands include: 'show version', 'systemctl status', or check the device management interface for the product name (Multipoint Switch, System 1300, System 3000, System 3010, System 3200, System 3210, Immersive Endpoint, Manager, or Recording Server).Affected if The device is any of the affected TelePresence product lines listed in the CVE.
-
Determine the software versionRun 'show version' on the device CLI, or access the web admin interface to find the software/firmware version. For Multipoint Switch, look for version numbers like 1.x.x.Affected if The installed version matches any version listed in the CVE affected versions, or for products marked 'all versions', any version is vulnerable.
-
Verify CDP is enabledCheck if Cisco Discovery Protocol is active. On most devices, run 'show cdp neighbor' or 'show cdp' from the CLI. In the web interface, look under Network or Interface settings for CDP configuration.Affected if CDP is enabled and the device is directly accessible on the network segment ( Layer 2 adjacency).
-
Assess network exposureDetermine if untrusted physical or network access is possible. Check which devices can send CDP packets to the affected device. Verify if the network segment where the TelePresence device resides is properly segmented or has access controls.Affected if The device is on a network segment where untrusted or unauthorized devices can send CDP frames directly to the affected device.
A user is affected if they run any of the listed TelePresence products at the specified versions (or any version for 'all versions' entries) with CDP enabled and with network adjacency possible from untrusted hosts.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor-supplied software updates: TelePresence Multipoint Switch to 1.9.0+, Immersive Endpoint Devices to 1.9.1+, Manager to 1.9.0+, and Recording Server to 1.8.1+. As a compensating control, restrict physical/network access to limit which hosts can send CDP packets.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-2486 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2012-2486 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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