Unified Communications ManagerApplication · Cisco
CVE-2014-3338
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 · uneditedThe CTIManager module in Cisco Unified Communications Manager (CM) 10.0(1), when single sign-on is enabled, does not properly validate Kerberos SSO tokens, which allows remote authenticated users to gain privileges and execute arbitrary commands via crafted token data, aka Bug ID CSCum95491.
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 confidenceThe CTIManager module in Cisco Unified Communications Manager 10.0(1) contains a validation flaw in its Kerberos SSO token handling when single sign-on is enabled. An authenticated remote attacker can submit crafted token data to bypass validation checks, thereby gaining elevated privileges and the ability to execute arbitrary commands on the affected 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
Unified Communications ManagerApplication
= 10.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
- M
- Authentication
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/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 Unified Communications Manager versionAccess the CUCM administration console and navigate to About > Version, or use the CLI command 'show version' via SSH to confirm the installed CUCM version.Affected if The installed version is exactly 10.0(1). Versions other than 10.0(1) are not affected by this specific CVE.
-
Verify CTIManager service statusIn CUCM Administration, go to Cisco Unified Serviceability > Service Activation, or use the CLI command 'show process list' to confirm CTIManager is running.Affected if CTIManager service is active and running on the system.
-
Confirm Single Sign-On is enabledIn CUCM Administration, navigate to System > SSO Configuration, or check the Cisco DirSync service configuration to determine if SSO is currently enabled.Affected if SSO is enabled. The vulnerability only applies when SSO is active, as it exploits the Kerberos SSO token validation flaw.
-
Check Kerberos SSO configurationReview the SSO configuration page to confirm Kerberos-based SSO is in use. The flaw specifically affects Kerberos SSO token handling in CTIManager.Affected if Kerberos SSO is configured and active. This is the specific token mechanism exploited by this vulnerability.
A system is affected if it runs Cisco Unified Communications Manager version 10.0(1) with CTIManager active and Kerberos-based SSO 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 Cisco patch for bug ID CSCum95491 or upgrade to a fixed version of CUCM. If immediate patching is not feasible, consider disabling SSO until the fix can be deployed, though this may impact business operations.
Fix this in Unified Communications Manager
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-3338 — 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-2014-3338 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