dbcve.org
Unity ConnectionApplication · Cisco

CVE-2015-0612

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)SU6, 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 (SIP outage) via a crafted UDP packet, aka Bug ID CSCuh25062.

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 versions 8.5 before 8.5(1)SU6, 8.6 before 8.6(2a)SU4, and 9.x before 9.1(2)SU2 is vulnerable to a denial of service when SIP trunk integration is enabled. Remote attackers can send a crafted UDP packet to trigger a SIP outage.

MitigationUpgrade Cisco Unity Connection to version 8.5(1)SU6, 8.6(2a)SU4, or 9.1(2)SU2 or later. As a workaround, disable SIP trunk integration or restrict UDP traffic to the SIP ports if upgrade 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.6\(1\)= 8.6\(1a\)= 8.6\(2\)= 8.6\(2a\)= 8.6\(2a\)su1= 8.6\(2a\)su2
Unity Connection 8.5Application
Affected:= base
Unity Connection 8.6Application
Affected:= base

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 Cisco Unity Connection installation
    Run 'utils service list' or check for CuCsMgr process via 'show process list' on the Cisco Unity Connection server
    Affected if CuCsMgr process is not running or Cisco Unity Connection is not installed
  2. Determine installed Cisco Unity Connection version
    Execute 'show version' or access the Cisco Unity Connection Administration page under About > System Information to retrieve the exact version number
    Affected if Version matches 8.5(x) before 8.5(1)SU6, 8.6(x) before 8.6(2a)SU4, or 9.x before 9.1(2)SU2
  3. Verify SIP trunk integration status
    Access Cisco Unity Connection Administration, navigate to Telephony Integration > SIP Trunk, or run 'run sql select * from sip_trunk' to check if any SIP trunks are configured and enabled
    Affected if SIP trunk integration is enabled and at least one SIP trunk is configured
  4. Confirm UDP exposure on SIP ports
    Check firewall or network ACLs for open UDP ports 5060-5061 (typical SIP ports) on the Unity Connection server
    Affected if UDP traffic is permitted to SIP ports from untrusted networks

You are affected if Cisco Unity Connection version is 8.5 before 8.5(1)SU6, 8.6 before 8.6(2a)SU4, or 9.x before 9.1(2)SU2 AND SIP trunk integration is enabled, allowing remote attackers to send crafted UDP packets to cause denial of service.

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 Unity Connection to version 8.5(1)SU6, 8.6(2a)SU4, or 9.1(2)SU2 or later. As a workaround, disable SIP trunk integration or restrict UDP traffic to the SIP ports if upgrade is not immediately feasible.

Fix this in Unity Connection Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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