dbcve.org
Unified Communications ManagerApplication · Cisco

CVE-2011-2564

HIGH · 7.8 CVSS v2.0 Published 2011-08-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Unspecified vulnerability in the Service Advertisement Framework (SAF) in Cisco Unified Communications Manager (aka CUCM, formerly CallManager) 8.x before 8.5(1) and Cisco Intercompany Media Engine 8.x before 8.5(1) allows remote attackers to cause a denial of service (device reload) via crafted SAF packets, aka Bug ID CSCth19417.

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

A denial of service vulnerability exists in the Service Advertisement Framework (SAF) component of Cisco Unified Communications Manager 8.x before 8.5(1) and Cisco Intercompany Media Engine 8.x before 8.5(1). Remote attackers can send specially crafted SAF packets to cause affected devices to reload, resulting in service disruption.

MitigationUpgrade Cisco Unified Communications Manager and Cisco Intercompany Media Engine to version 8.5(1) or later to remediate this vulnerability. If immediate patching is not possible, consider network segmentation to limit exposure to untrusted SAF traffic.

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
Unified Communications ManagerApplication
Affected:= 8.0= 8.0\(1\)= 8.0\(2c\)= 8.0\(2c\)su1= 8.0\(3\)= 8.0\(3a\)= 8.0\(3a\)su1= 8.0\(3a\)su2= 8.5
Intercompany Media EngineApplication
Affected:= 8.0\(2\)= 8.0\(3\)

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 the installed product
    Determine whether Cisco Unified Communications Manager (CUCM) or Cisco Intercompany Media Engine (IME) is installed in your environment. Check the system inventory or use 'show version' on the CLI if you have access.
    Affected if Either CUCM or IME is present on the network
  2. Check CUCM version
    On the CUCM server, run the CLI command 'show version' or access the Disaster Recovery System to view the installed version. Compare the version number against 8.5(1).
    Affected if CUCM version is 8.0, 8.0(1), 8.0(2c), 8.0(2c)su1, 8.0(3), 8.0(3a), 8.0(3a)su1, 8.0(3a)su2, or 8.5 (i.e., any 8.x version before 8.5(1))
  3. Check IME version
    On the IME server, run the CLI command 'show version' or access the Disaster Recovery System to view the installed version. Compare the version number against 8.5(1).
    Affected if IME version is 8.0(2), 8.0(3), or any 8.x version before 8.5(1)
  4. Verify if SAF is enabled
    In CUCM, navigate to System > Service Parameters and check for SAF-related services (such as Cisco Service Advertisement Framework or Call Control Discovery). Alternatively, use the CLI command 'show service' to list active services.
    Affected if SAF or Call Control Discovery service is enabled and running on the affected version

You are affected if you are running CUCM or IME version 8.x before 8.5(1) with the SAF component enabled and exposed to network traffic.

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

Upgrade Cisco Unified Communications Manager and Cisco Intercompany Media Engine to version 8.5(1) or later to remediate this vulnerability. If immediate patching is not possible, consider network segmentation to limit exposure to untrusted SAF traffic.

Fix this in Unified Communications Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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