dbcve.org
Unified Communications ManagerApplication · Cisco

CVE-2011-4487

MEDIUM · 6.8 CVSS v2.0 Published 2012-03-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/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
SQL injection vulnerability in Cisco Unified Communications Manager (CUCM) with software 6.x and 7.x before 7.1(5b)su5, 8.0 before 8.0(3a)su3, and 8.5 and 8.6 before 8.6(2a)su1 and Cisco Business Edition 3000 with software before 8.6.3 and 5000 and 6000 with software before 8.6(2a)su1 allows remote attackers to execute arbitrary SQL commands via a crafted SCCP registration, aka Bug ID CSCtu73538.

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

SQL injection vulnerability in Cisco Unified Communications Manager (CUCM) allows remote attackers to execute arbitrary SQL commands via crafted SCCP (Skinny Call Control Protocol) registration messages. The vulnerability exists in the SCCP registration handling code and affects versions 6.x, 7.x before 7.1(5b)su5, 8.0 before 8.0(3a)su3, 8.5 and 8.6 before 8.6(2a)su1, and Cisco Business Edition versions.

MitigationApply the vendor-supplied patches (7.1(5b)su5, 8.0(3a)su3, 8.6(2a)su1, or 8.6.3 depending on current version) to close the SQL injection vector in SCCP registration. If patching is not immediately feasible, consider network segmentation to limit exposure to untrusted SCCP 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:= 6.0= 6.0\(1\)= 6.0\(1a\)= 6.0\(1b\)= 6.1\(1\)= 6.1\(1a\)= 6.1\(1b\)= 6.1\(2\)= 6.1\(2\)su1= 6.1\(2\)su1a= 6.1\(3\)= 6.1\(3a\)
Business Edition 3000 SoftwareApplication
Affected:= 8.6\(1\)= 8.6\(1a\)= 8.6\(2a\)= 8.6.2
Business Edition 3000Hardware / appliance
Affected:all versions
Business Edition 5000 SoftwareApplication
Affected:= 8.5= 8.5\(1\)= 8.6= 8.6\(1\)= 8.6\(1a\)= 8.6\(2\)= 8.6\(2a\)
Business Edition 5000Hardware / appliance
Affected:all versions
Business Edition 6000 SoftwareApplication
Affected:= 8.5\(1\)= 8.5\(1\)su1= 8.5\(1\)su2= 8.5\(1\)su3= 8.5\(1-2011o\)= 8.6\(1\)= 8.6\(1a\)= 8.6\(2\)= 8.6\(2a\)
Business Edition 6000Hardware / 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
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/Au:N/C:P/I:P/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 CUCM version
    Log into the CUCM CLI and run 'show version' or access the Cisco Unified CM Administration page and check the About page
    Affected if The displayed version matches any of the affected versions listed in the CVE (6.x, 7.x before 7.1(5b)su5, 8.0 before 8.0(3a)su3, 8.5, or 8.6 before 8.6(2a)su1)
  2. Confirm SCCP protocol is enabled
    In CUCM Administration, navigate to System > Protocol > SCCP or use CLI 'show sccp connections' to see if any SCCP devices are registered
    Affected if SCCP is actively enabled or has registered devices (phones or gateways) in the environment
  3. Check Cisco Business Edition version
    If using Cisco Business Edition 3000, 5000, or 6000, check the version via CLI 'show version' or the Administration About page
    Affected if The Business Edition version matches any of the specific software versions listed in the CVE for BE3000, BE5000, or BE6000

You are affected if your CUCM or Business Edition version falls within the vulnerable ranges AND SCCP protocol is enabled in your environment.

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 the vendor-supplied patches (7.1(5b)su5, 8.0(3a)su3, 8.6(2a)su1, or 8.6.3 depending on current version) to close the SQL injection vector in SCCP registration. If patching is not immediately feasible, consider network segmentation to limit exposure to untrusted SCCP 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-4487 — 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-4487 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