Unified Communications ManagerApplication · Cisco
CVE-2016-9210
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 · uneditedA vulnerability in the Cisco Unified Reporting upload tool accessed via the Cisco Unified Communications Manager could allow an unauthenticated, remote attacker to modify arbitrary files on the file system. More Information: CSCvb61698. Known Affected Releases: 11.5(1.11007.2). Known Fixed Releases: 12.0(0.98000.168) 12.0(0.98000.178) 12.0(0.98000.399) 12.0(0.98000.510) 12.0(0.98000.536) 12.0(0.98500.7).
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 confidenceA path traversal vulnerability in the Cisco Unified Reporting upload tool within Cisco Unified Communications Manager allows an unauthenticated, remote attacker to write files to arbitrary locations on the filesystem due to insufficient validation of user-supplied input in the upload function.
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\(1.11007.2\)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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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 the installed Cisco Unified Communications Manager versionLog into the CUCM admin interface and navigate to About > Version, or use the CLI command 'show version' to retrieve the exact version number.Affected if The installed version is exactly 11.5(1.11007.2)
-
Verify Cisco Unified Reporting service is enabledAccess the Cisco Unified Serviceability page and check if the Cisco Unified Reporting service is listed as running. Alternatively, attempt to access the Cisco Unified Reporting web interface at https://<server>/curreporting/.Affected if The Cisco Unified Reporting service is running and responding to requests
-
Confirm network accessibility of the upload endpointReview network access controls, firewall rules, and ACLs to determine if the Cisco Unified Reporting upload functionality (typically at the /curreporting/ endpoint) is accessible from untrusted networks or the internet.Affected if The upload functionality is exposed to network access beyond trusted administrative networks
A system is affected if it is running Cisco Unified Communications Manager version 11.5(1.11007.2) with the Cisco Unified Reporting service enabled and its upload function accessible to the network where the vulnerability can be exploited.
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 appropriate fixed release (12.0(0.98000.168) or later) or implement network-level access controls to restrict access to the Cisco Unified Reporting service until patching can be completed.
Fix this in Unified Communications Manager
Scoped from the published advisory
- Consultation4.0 h
- Implementation12.0 h
- Testing4.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 $6,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-9210 — 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-9210 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