Unified Communications ManagerApplication · Cisco
CVE-2011-1604
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 · uneditedMemory leak in Cisco Unified Communications Manager (aka CUCM, formerly CallManager) 6.x before 6.1(5)su3, 7.x before 7.1(5b)su3, 8.0 before 8.0(3a)su2, and 8.5 before 8.5(1) allows remote attackers to cause a denial of service (memory consumption and process failure) via a malformed SIP message, aka Bug ID CSCti42904.
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 memory leak vulnerability in Cisco Unified Communications Manager allows remote attackers to cause denial of service by sending malformed SIP messages. The vulnerability affects versions 6.x before 6.1(5)su3, 7.x before 7.1(5b)su3, 8.0 before 8.0(3a)su2, and 8.5 before 8.5(1). The malformed SIP messages cause memory consumption that leads to process failure.
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
= 6.0= 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\)= 6.1\(3b\)= 6.1\(3b\)su1= 6.1\(4\)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
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:M/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed CUCM versionAccess the Cisco Unified Communications Manager Administration interface and navigate to System > Version, or use the CLI command 'show version' via SSH to determine the exact CUCM version numberAffected if The installed version falls within these ranges: 6.x before 6.1(5)su3, 7.x before 7.1(5b)su3, 8.0 before 8.0(3a)su2, or 8.5 before 8.5(1)
-
Verify SIP service is enabledCheck in CUCM Administration under Service > Service Parameters for the Cisco SIP Proxy service, or verify SIP trunk or device configurations are activeAffected if SIP service, SIP trunks, or SIP-enabled devices are configured and running, as the vulnerability is in SIP message processing
-
Check for symptoms of the memory leakMonitor system memory usage via CLI using 'show process memory sorted' or in the admin interface. Look for abnormally high memory consumption by the SIP-related processesAffected if SIP proxy or related processes are consuming excessive memory or experiencing frequent restarts or failures
A user is affected if their CUCM version matches one of the vulnerable version ranges AND SIP service is enabled, as the memory leak only triggers when processing malformed SIP messages.
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 the vendor-supplied software updates (service updates) for the affected CUCM versions to patch the memory leak vulnerability in the SIP processing component.
Fix this in Unified Communications Manager
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-1604 — 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-2011-1604 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