Unified Communications ManagerApplication · Cisco
CVE-2018-0105
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 web framework of Cisco Unified Communications Manager could allow an unauthenticated, remote attacker to view sensitive data. The vulnerability is due to insufficient protection of database tables. An attacker could exploit this vulnerability by browsing to a specific URL. An exploit could allow the attacker to view data library information. Cisco Bug IDs: CSCvf20269.
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 confidenceA vulnerability in the web framework of Cisco Unified Communications Manager allows an unauthenticated, remote attacker to view sensitive data by browsing to a specific URL. The issue stems from insufficient protection of database tables, enabling exposure of data library information.
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
all versionsCVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 the Cisco Unified Communications Manager versionLog into the CUCM Administrative UI and navigate to About > Product Information, or use the CLI command 'show version' to retrieve the installed version numberAffected if The system is running any version of Cisco Unified Communications Manager without patch CSCvf20269 applied
-
Verify patch CSCvf20269 is installedUsing the CUCM CLI, run 'show patch' or access the Cisco Unified OS Administration interface to view installed patches; locate entry for patch ID CSCvf20269 in the patch listAffected if Patch CSCvf20269 is not listed among installed patches
-
Confirm web framework is accessibleAttempt to access the CUCM web interface from an untrusted network or verify firewall rules allow external access to ports 443/8443 used by the CUCM web frameworkAffected if The CUCM web interface (HTTPS on port 443 or 8443) is accessible from untrusted networks without proper network segmentation
-
Review web server access logs for suspicious URLsExamine CUCM web logs (typically located in /var/log/httpd/ or accessible via RTMT) for repeated requests to unusual database table URLs or paths that may indicate exploitation attemptsAffected if Logs show unauthorized access attempts to sensitive database table URLs or unexpected data exposure requests
The environment is affected if Cisco Unified Communications Manager is running without patch CSCvf20269 and the web framework is network-accessible.
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 CSCvf20269 to the Unified Communications Manager. If a patch is unavailable, consider restricting web framework access via network segmentation or firewall rules to limit exposure.
Fix this in Unified Communications Manager
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0105 — 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-2018-0105 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