Unified Communications ManagerApplication · Cisco
CVE-2016-6440
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 Cisco Unified Communications Manager (CUCM) may be vulnerable to data that can be displayed inside an iframe within a web page, which in turn could lead to a clickjacking attack. More Information: CSCuz64683 CSCuz64698. Known Affected Releases: 11.0(1.10000.10), 11.5(1.10000.6), 11.5(0.99838.4). Known Fixed Releases: 11.0(1.22048.1), 11.5(0.98000.1070), 11.5(0.98000.284)11.5(0.98000.346), 11.5(0.98000.768), 11.5(1.10000.3), 11.5(1.10000.6), 11.5(2.10000.2).
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 Unified Communications Manager (CUCM) is vulnerable to clickjacking attacks due to the application being displayable within an iframe on arbitrary web pages. This allows attackers to overlay invisible or disguised UI elements, tricking authenticated users into performing unintended actions such as changing administrative settings or making calls.
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
= 11.5\(0.99838.4\)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
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
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 CUCM versionAccess the Cisco Unified Communications Manager admin interface and navigate to About > License or use the 'show version' command via CLI (admin: show version) to determine the installed CUCM versionAffected if The installed version is 11.5(0.99838.4) or any version prior to 11.5(0.98000.1070) or 11.0(1.22048.1)
-
Check if web interface allows framingCreate a simple HTML page with an iframe pointing to the CUCM login page (for example: <iframe src='https://CUCM_HOSTNAME/ccmadmin/'> and open it in a browser to see if the CUCM interface loads inside the iframeAffected if The CUCM login or admin pages load successfully inside the iframe from an external domain
-
Inspect HTTP response headersUse browser developer tools (Network tab), curl (curl -I https://CUCM_HOSTNAME/ccmadmin/), or a header inspection tool to examine the HTTP responses from the CUCM web interface for X-Frame-Options and Content-Security-Policy headersAffected if The response headers do not include X-Frame-Options: DENY or X-Frame-Options: SAMEORIGIN, and there is no Content-Security-Policy header with frame-ancestors directive
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 fixed CUCM releases (11.0(1.22048.1), 11.5(0.98000.1070) or later) which implement proper X-Frame-Options or frame-ancestors Content-Security-Policy directives, or configure the web server/load balancer to send X-Frame-Options: DENY or SAMEORIGIN headers as a workaround.
Fix this in Unified Communications Manager
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-6440 — 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-2016-6440 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