dbcve.org
Unity ConnectionApplication · Cisco

CVE-2015-0613

HIGH · 7.1 CVSS v2.0 Published 2015-04-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/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
The Connection Conversation Manager (aka CuCsMgr) process in Cisco Unity Connection 8.5 before 8.5(1)SU7, 8.6 before 8.6(2a)SU4, 9.x before 9.1(2)SU2, and 10.0 before 10.0(1)SU1, when SIP trunk integration is enabled, allows remote attackers to cause a denial of service (core dump and restart) via crafted SIP INVITE messages, aka Bug ID CSCul20444.

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 Connection Conversation Manager (CuCsMgr) process in Cisco Unity Connection contains a vulnerability when processing SIP INVITE messages on systems with SIP trunk integration enabled. Attackers can send specially crafted SIP INVITE messages to trigger a core dump and process restart, causing denial of service.

MitigationApply the appropriate Cisco Unity Connection Software Update (SU7 for 8.5, SU4 for 8.6, SU2 for 9.x, SU1 for 10.0) to patch the vulnerability. As a workaround, disable SIP trunk integration if patching is not immediately feasible.

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
Affected:= 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Cisco Unity Connection version
    Run the command 'show version' in the Cisco Unity Connection CLI or check the version through the Unity Connection Administration interface under System > Settings > Version. Compare the version number against the affected list: 8.5(1), 8.5(1)su1-su6, 8.6(1), 8.6(1a), 8.6(2), 8.6(2a).
    Affected if The installed version matches any of the listed affected versions.
  2. Confirm SIP trunk integration is enabled
    Access Unity Connection Administration and navigate to Telephony Integration > SIP Trunk or use the CLI command 'show sip trunk' to list active SIP trunks. Verify if any SIP trunk is configured and in service.
    Affected if At least one SIP trunk is enabled and configured in the system.
  3. Review CuCsMgr process logs for crashes
    Check the Unity Connection server logs for CuCsMgr process failures using 'file list' in the CLI to access log directories, or review any core dump files in /var/log/active/ or similar log paths. Look for entries indicating unexpected CuCsMgr restarts or core dumps around the time of any SIP INVITE processing.
    Affected if CuCsMgr process crashes or core dumps are observed in the logs.
  4. Verify SIP INVITE message handling
    If SIP logging is enabled, review SIP trace logs for any malformed or specially crafted SIP INVITE messages that may have triggered the vulnerability. Check for SIP INVITE messages that caused the CuCsMgr process to fail.
    Affected if SIP INVITE messages are being processed and have caused process failures.

The environment is affected if Cisco Unity Connection version is one of the listed affected versions AND SIP trunk integration is enabled, allowing specially crafted SIP INVITE messages to reach the CuCsMgr process.

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 appropriate Cisco Unity Connection Software Update (SU7 for 8.5, SU4 for 8.6, SU2 for 9.x, SU1 for 10.0) to patch the vulnerability. As a workaround, disable SIP trunk integration if patching is not immediately feasible.

Fix this in Unity Connection Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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