Unified Communications ManagerApplication · Cisco
CVE-2013-3412
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 · uneditedSQL injection vulnerability in Cisco Unified Communications Manager (CUCM) 7.1(x) through 9.1(2) allows remote authenticated users to execute arbitrary SQL commands via unspecified vectors, aka Bug ID CSCuh81766.
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 confidenceSQL injection vulnerability in Cisco Unified Communications Manager (CUCM) versions 7.1(x) through 9.1(2) allows remote authenticated users to execute arbitrary SQL commands via unspecified input vectors. The vulnerability stems from improper sanitization of user-supplied data in backend database queries.
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
Unified Communications ManagerApplication
= 7.1\(2a\)= 7.1\(2a\)su1= 7.1\(2b\)= 7.1\(2b\)su1= 7.1\(3\)= 7.1\(3a\)= 7.1\(3a\)su1= 7.1\(3a\)su1a= 7.1\(3b\)= 7.1\(3b\)su1= 7.1\(3b\)su2= 7.1\(5\)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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/C:P/I:P/A:P
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.
-
Confirm CUCM installationLog into the CUCM server via SSH or access the Cisco Unified Communications Manager Administration web interface. If you cannot locate the product, it is not installed.Affected if CUCM is not present in the environment, the system is not affected.
-
Identify the installed CUCM versionFrom the CLI, run 'show version' or 'utils system version'. Alternatively, log into the Administration web interface and check the 'About' page or 'System > Version' for the precise version number.Affected if The installed version falls within 7.1(x) through 9.1(2), including any 7.1(2a), 7.1(2b), 7.1(3), 7.1(3a), 7.1(3b), or 7.1(5) release, or any 8.x or 9.0/9.1(1)/9.1(2) version.
-
Verify the admin interface is reachableConfirm the Cisco Unified Communications Manager Administration web interface (typically port 8443 or 443) is accessible on the network. Attempt a login to the administration console.Affected if The admin interface is exposed and accepts authentication credentials.
-
Confirm authentication is enabled and activeEnsure user authentication is not disabled and verify that local database access or LDAP integration is configured for administrative logins.Affected if Administrative user accounts exist and can authenticate to the system.
The environment is affected if Cisco Unified Communications Manager is running any version from 7.1(x) through 9.1(2) and the administration interface with user authentication is enabled.
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 patch from Cisco (referenced by Bug ID CSCuh81766) or upgrade to a CUCM version beyond 9.1(2). As a compensating control, restrict administrative access to trusted personnel only and monitor database query logs for suspicious activity.
Fix this in Unified Communications Manager
Scoped from the published advisory
- Consultation4.0 h
- Implementation12.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 $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-3412 — 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-2013-3412 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