CVE-2019-15963
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-based management interface of Cisco Unified Communications Manager could allow an authenticated, remote attacker to view sensitive information in the web-based management interface of the affected software. The vulnerability is due to insufficient protection of user-supplied input by the web-based management interface of the affected service. An attacker could exploit this vulnerability by accessing the interface and viewing restricted portions of the software configuration. A successful exploit could allow the attacker to gain access to sensitive information or conduct further attacks.
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 confidenceThis is an information disclosure vulnerability in Cisco Unified Communications Manager's web-based management interface. An authenticated remote attacker can view sensitive configuration data that should be restricted. The vulnerability stems from insufficient protection of user-supplied input, likely allowing unauthorized access to restricted pages or parameters through the web interface.
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>= 10.5, <= 10.5\(2.10000.5\)>= 11.5, <= 11.5\(1.10000.6\)>= 12.0, <= 12.0\(1.10000.10\)>= 12.5, <= 12.5\(1.10000.22\)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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 installed Cisco Unified Communications Manager versionLog into the server via CLI and run the command 'show version' or access the web interface and navigate to Help > About to view the version information.Affected if The displayed version falls within these ranges: 10.5 through 10.5(2.10000.5), 11.5 through 11.5(1.10000.6), 12.0 through 12.0(1.10000.10), or 12.5 through 12.5(1.10000.22).
-
Confirm the web-based management interface is enabled and accessibleAttempt to access the Cisco Unified Communications Manager web interface via HTTPS at the primary node's hostname or IP address on port 443 (for example, https://<hostname>/ccmadmin or https://<IP>/ccmadmin).Affected if The web management interface responds and is reachable from the network segment being tested.
-
Verify authentication is required for the web interfaceAttempt to access the web management pages without providing credentials. Observe whether the system redirects to a login page or denies access.Affected if The interface requires authentication but the vulnerability is exploited after obtaining any valid administrative credentials.
-
Review administrative user accounts with web interface accessUse the Cisco Unified Communications Operating System Administration console or CLI command 'show cucm list user' to enumerate accounts that have administrative privileges for the web interface.Affected if Any administrative user accounts exist that could be used to authenticate to the vulnerable web interface.
You are affected if your installed Cisco Unified Communications Manager version falls within the listed vulnerable ranges AND the web-based management interface is network-accessible to potential attackers.
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 Cisco's official patch for CVE-2019-15963 when available. Until then, restrict network access to the web-based management interface using network segmentation and access controls, and limit the number of users with administrative credentials.
- Consultation2.0 h
- Implementation4.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15963 — 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-2019-15963 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