dbcve.org
Unity ConnectionApplication · Cisco

CVE-2012-0367

HIGH · 7.8 CVSS v2.0 Published 2012-03-01
Fix available
A fix is available. Upgrade to after 7.1 or later.
See remediation →
87/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
Cisco Unity Connection before 7.1.5b(Su5), 8.0 and 8.5 before 8.5.1(Su3), and 8.6 before 8.6.2 allows remote attackers to cause a denial of service (services crash) via a series of crafted TCP segments, aka Bug ID CSCtq67899.

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 · moderate confidence

Cisco Unity Connection versions prior to 7.1.5b(Su5), 8.5.1(Su3), and 8.6.2 contain a denial of service vulnerability where remote attackers can cause services to crash by sending a series of crafted TCP segments to the affected system.

MitigationUpgrade Cisco Unity Connection to version 7.1.5b(Su5), 8.5.1(Su3), 8.6.2 or later per Cisco's official advisories. If immediate patching is not possible, consider network segmentation to limit exposure to untrusted networks.

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:<= 7.1\(5b\)su4= 1.1= 1.1\(1\)= 1.1\(1\)_es1= 1.1\(1\)_es12= 1.1\(1\)_sr1= 1.2= 1.2\(1\)= 1.2\(1\)_es65= 1.2\(1\)sr2= 2.0= 2.0\(1\)

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
Low
Authentication
None
Confidentiality
None
Integrity
None
Availability
Complete

AV:N/AC:L/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. Verify Cisco Unity Connection is installed
    Check the system for Cisco Unity Connection installation. On the server, run 'utils service list' or check for Unity Connection processes via the CLI command 'show process list' if you have administrative access.
    Affected if The product is not installed or not running Cisco Unity Connection.
  2. Identify the installed version
    Access the Cisco Unity Connection CLI and run 'show version' or access the admin web interface and navigate to About page to view the exact version number (e.g., 7.1(5b)su4, 8.5.1, 8.6.1, etc.).
    Affected if The installed version is 7.1(5b)su4 or earlier, or matches any of these specific versions: 1.1, 1.1(1), 1.1(1)_es1, 1.1(1)_es12, 1.1(1)_sr1, 1.2, 1.2(1), 1.2(1)_es65, 1.2(1)sr2, 2.0, or 2.0(1).
  3. Confirm network exposure
    Determine if the Cisco Unity Connection server is directly accessible from untrusted networks. Check firewall rules, ACLs, and network segmentation to see if TCP ports used by Unity Connection (typically ports 80, 443, 5060, 5061 for web and SIP) are exposed to the internet or untrusted segments.
    Affected if The Unity Connection web interface or SIP ports are accessible from untrusted networks without proper filtering.
  4. Review for service crashes
    Check system logs and Unity Connection specific logs for unexpected service restarts or crashes. Use CLI command 'show logs' or access the Serviceability interface to review event logs around the timeframe of any incidents.
    Affected if There are unexplained service crashes or restarts, particularly in the SIP or web services.

You are affected if Cisco Unity Connection is installed and the version falls within the affected ranges (7.1(5b)su4 and earlier, or versions 1.1 through 2.0(1) as listed), AND the system is network-accessible to potential attackers.

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
Upgrade available Upgrade to a release after 7.1
Interim mitigation

Upgrade Cisco Unity Connection to version 7.1.5b(Su5), 8.5.1(Su3), 8.6.2 or later per Cisco's official advisories. If immediate patching is not possible, consider network segmentation to limit exposure to untrusted networks.

Fix this in Unity Connection Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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