dbcve.org
Ip CommunicatorApplication · Cisco

CVE-2012-0361

MEDIUM · 5.0 CVSS v2.0 Published 2012-05-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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 sccp-protocol component in Cisco IP Communicator (CIPC) 7.0 through 8.6 does not limit the rate of SCCP messages to Cisco Unified Communications Manager (CUCM), which allows remote attackers to cause a denial of service via vectors that trigger (1) on hook and (2) off hook messages, as demonstrated by a Plantronics headset, aka Bug ID CSCti40315.

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 SCCP (Skinny Client Control Protocol) implementation in Cisco IP Communicator versions 7.0 through 8.6 lacks proper rate limiting on SCCP messages sent to Cisco Unified Communications Manager. A remote attacker or compromised device (such as a maliciously configured headset) can flood CUCM with rapid on-hook and off-hook SCCP messages, causing a denial of service condition.

MitigationApply available Cisco patches for CIPC and CUCM. Additionally, implement network-level controls such as SCCP traffic rate limiting or ACLs on voice VLANs to restrict anomalous SCCP message bursts from 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
Ip CommunicatorApplication
Affected:= 7.0= 7.0\(1\)= 7.0\(2\)= 7.0\(3\)= 7.0\(4\)= 7.0\(5\)= 7.0\(6\)= 8.6

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
Partial

AV:N/AC:L/Au:N/C:N/I:N/A:P

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 IP Communicator installation
    Check system for Cisco IP Communicator installation by looking in Program Files (Windows) or /Applications (Mac) for 'Cisco IP Communicator' folder, or check Windows Registry under HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall for Cisco IP Communicator entry
    Affected if Cisco IP Communicator is installed on the system
  2. Determine installed CIPC version
    Launch Cisco IP Communicator, go to Help > About, or check the version in the application window title bar or in Add/Remove Programs. Compare the version number against the affected range: 7.0, 7.0(1), 7.0(2), 7.0(3), 7.0(4), 7.0(5), 7.0(6), and 8.6
    Affected if The installed version matches one of the affected versions listed (7.0 through 8.6)
  3. Confirm SCCP protocol is in use
    In Cisco IP Communicator, go to File > Preferences > Protocol or Device > Device Settings to verify SCCP (Skinny) is selected as the protocol instead of SIP. SCCP must be enabled for this vulnerability to apply
    Affected if SCCP (Skinny) protocol is selected and active
  4. Check CUCM server connection
    In Cisco IP Communicator, go to Device > Device Configuration or File > Preferences > Server to verify the device is registered to a Cisco Unified Communications Manager (CUCM) server. The vulnerability affects CUCM when flooded with SCCP messages from the endpoint
    Affected if CIPC is registered and actively communicating with a CUCM server

You are affected if Cisco IP Communicator versions 7.0 through 8.6 is installed with SCCP protocol enabled and registered to a CUCM server.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply available Cisco patches for CIPC and CUCM. Additionally, implement network-level controls such as SCCP traffic rate limiting or ACLs on voice VLANs to restrict anomalous SCCP message bursts from endpoints.

Fix this in Ip Communicator Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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