Unity ConnectionApplication · Cisco
CVE-2015-0616
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 Connection Conversation Manager (aka CuCsMgr) process in Cisco Unity Connection 8.5 before 8.5(1)SU7, 8.6 before 8.6(2a)SU4, and 9.x before 9.1(2)SU2, when SIP trunk integration is enabled, allows remote attackers to cause a denial of service (core dump and restart) by improperly terminating SIP TCP connections, aka Bug ID CSCul69819.
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 confidenceThe Connection Conversation Manager (CuCsMgr) process in Cisco Unity Connection versions 8.5 before 8.5(1)SU7, 8.6 before 8.6(2a)SU4, and 9.x before 9.1(2)SU2 contains a denial of service vulnerability when SIP trunk integration is enabled. Attackers can trigger a crash by improperly terminating SIP TCP connections, causing the process to dump core and restart.
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
Unity ConnectionApplication
= 8.5\(1\)= 8.5\(1\)su1= 8.5\(1\)su2= 8.5\(1\)su3= 8.5\(1\)su4= 8.5\(1\)su5= 8.5\(1\)su6= 8.5_base= 8.6\(1\)= 8.6\(1a\)= 8.6\(2\)= 8.6\(2a\)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 Cisco Unity Connection versionRun 'show version' on the Unity Connection server or access the Cisco Unity Connection Administration page to view the system version informationAffected if The installed version is 8.5(1) through 8.5(1)SU6, 8.6(1), 8.6(1a), 8.6(2), or 8.6(2a)
-
Determine if SIP trunk integration is enabledAccess Cisco Unity Connection Administration, navigate to Telephony Integration > SIP Trunk or use the CLI command 'show sip trunk' to check for configured SIP trunksAffected if SIP trunk integration is enabled and active on the system
-
Check for CuCsMgr process crashesReview system logs or core dump files in /var/log/active/ or use 'show process' CLI command to look for recent CuCsMgr process restartsAffected if CuCsMgr process has crashed or generated core dumps recently
-
Verify SIP TCP connection handlingMonitor SIP TCP connections on port 5060/5061 or review SIP debug logs for abnormally terminated connectionsAffected if SIP TCP connections are being improperly terminated or causing errors
You are affected if running any of the listed 8.5 or 8.6 versions AND SIP trunk integration is enabled, as both conditions must be present for this denial of service vulnerability to be exploitable.
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 (8.5(1)SU7, 8.6(2a)SU4, or 9.1(2)SU2) to patch this vulnerability. Until patched, consider disabling SIP trunk integration or restricting network access to the SIP interface.
Fix this in Unity Connection
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0616 — 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-2015-0616 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