dbcve.org
Unified Communications ManagerApplication · Cisco

CVE-2018-0411

MEDIUM · 6.1 CVSS v3.0 Published 2018-08-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
A vulnerability in the web-based management interface of Cisco Unified Communications Manager could allow an unauthenticated, remote attacker to conduct a reflected cross-site scripting (XSS) attack against a user of the web-based management interface of an affected device. The vulnerability is due to insufficient validation of user-supplied input by the web-based management interface of the affected software. An attacker could exploit this vulnerability by persuading a user of the interface to click a crafted link. A successful exploit could allow the attacker to execute arbitrary script code in the context of the interface or allow the attacker to access sensitive browser-based information. Cisco Bug IDs: CSCvk15343.

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 confidence

A reflected cross-site scripting (XSS) vulnerability exists in the web-based management interface of Cisco Unified Communications Manager due to insufficient validation of user-supplied input. An unauthenticated, remote attacker can exploit this by tricking a user into clicking a crafted link, allowing execution of arbitrary script code in the context of the interface or access to sensitive browser-based information.

MitigationApply the vendor patch from Cisco (refer to CSCvk15343) when available. Users should avoid clicking untrusted links to the management interface until the fix is applied.

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
Affected:= 10.5\(2.10000.5\)= 11.0\(1.10000.10\)= 11.5\(1.10000.6\)= 12.0\(1.10000.10\)

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Cisco Unified Communications Manager is installed
    Locate the Cisco Unified Communications Manager installation by checking for the product on the system, typically found in /opt/cisco or C:\Program Files\Cisco, or query the system for installed software named 'Cisco Unified Communications Manager' or 'CUCM'.
    Affected if The product is not installed on the system.
  2. Identify the installed CUCM version
    Access the web-based management interface and navigate to the About page, or run the command 'show version' via the CLI (SSH to the CUCM IP and authenticate). The version will display in format like 10.5(2), 11.0(1), 11.5(1), or 12.0(1).
    Affected if The version exactly matches 10.5(2.10000.5), 11.0(1.10000.10), 11.5(1.10000.6), or 12.0(1.10000.10).
  3. Verify the web-based management interface is enabled
    Confirm the Cisco Unified Communications Manager web interface is accessible by attempting to reach https://<CUCM-IP>/ccmadmin/ or the main login page. Check via CLI using 'show network eth0' to confirm HTTP/HTTPS services are running.
    Affected if The web management interface is exposed and accessible to network users.
  4. Check for indicators of exploitation attempts
    Review web server access logs (typically located in /var/log/httpd/ or /opt/cisco/cmplatform/log/) for suspicious URL patterns containing script tags, javascript:, or unusual parameters in requests to the management interface.
    Affected if Logs contain requests with XSS payload patterns targeting the management interface.

A system is affected only if Cisco Unified Communications Manager is installed with an exact version match to 10.5(2.10000.5), 11.0(1.10000.10), 11.5(1.10000.6), or 12.0(1.10000.10) AND the web-based management interface is accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch from Cisco (refer to CSCvk15343) when available. Users should avoid clicking untrusted links to the management interface until the fix is applied.

Fix this in Unified Communications Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-0411 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-0411 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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