Unity ConnectionApplication · Cisco
CVE-2012-0366
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 · uneditedCisco Unity Connection before 7.1.3b(Su2) allows remote authenticated users to change the administrative password by leveraging the Help Desk Administrator role, aka Bug ID CSCtd45141.
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 confidenceCisco Unity Connection versions prior to 7.1.3b(Su2) contain a privilege escalation vulnerability where a remote authenticated user with the Help Desk Administrator role can change the administrative password, effectively gaining full administrative control over the system.
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
<= 7.1\(3b\)su1= 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
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:S/C:C/I:C/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 installationCheck if Cisco Unity Connection is installed on the system. This is typically found on Cisco Unified Communications Manager servers. Use 'show version' or check system documentation to confirm Unity Connection presence.Affected if Cisco Unity Connection is not installed on the system.
-
Determine installed Unity Connection versionAccess the Cisco Unity Connection admin web interface or use CLI command 'show version' in the Cisco Unity Connection serviceability page to retrieve the exact version number.Affected if The installed version matches any of the following: versions prior to 7.1.3b(Su2), or 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, 2.0(1).
-
Verify Help Desk Administrator role existsIn Cisco Unity Connection admin interface, navigate to User Basics > User Templates > Role Management, or use CLI 'show cuc user role' to list defined roles including Help Desk Administrator.Affected if The Help Desk Administrator role is defined in the system.
-
Check for Help Desk Administrator user accountsIn Cisco Unity Connection admin interface, go to Users > Find to search for users assigned the Help Desk Administrator role, or use CLI 'show cuc user' to list users and their assigned roles.Affected if Any user account is assigned the Help Desk Administrator role.
A system is affected if Cisco Unity Connection is installed with a version listed in the affected versions range AND at least one user has the Help Desk Administrator role assigned.
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.
dbcve · scopedUpgrade Cisco Unity Connection to version 7.1.3b(Su2) or later to remediate this vulnerability. If immediate upgrade is not possible, restrict Help Desk Administrator role assignments and monitor for unauthorized password changes.
Cisco Unity Connection 7.1.3b(Su2) or later
- 1. Backup the current Cisco Unity Connection configuration and database before initiating any upgrade.
- 2. Download Cisco Unity Connection version 7.1.3b(Su2) or later from the Cisco Software Download Center (tools.cisco.com).
- 3. Review Cisco Unity Connection upgrade documentation and release notes for version 7.1.3b(Su2) for any prerequisites or migration requirements.
- 4. Schedule a maintenance window as upgrades may require system downtime.
- 5. Follow the standard Cisco Unity Connection upgrade procedure: run the upgrade installer, monitor for completion, and verify the new version is installed.
- 6. After upgrade, verify that the vulnerability is fixed by attempting to confirm the Help Desk Administrator role can no longer change administrative passwords.
- 7. Test critical Unity Connection services (voice messaging, call handlers, user access) to ensure normal operation.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Unity Connection
Scoped from the published advisory
- Consultation4.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,312.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0366 — 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-2012-0366 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