dbcve.org
Unified Communications ManagerApplication · Cisco

CVE-2020-3346

MEDIUM · 6.1 CVSS v3.1 Published 2020-08-17
Fix available
A fix is available. Upgrade to after 11.5 or later.
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 UI of Cisco Unified Communications Manager (Unified CM) and Cisco Unified Communications Manager Session Management Edition (Unified CM SME) could allow an unauthenticated, remote attacker to conduct a cross-site scripting (XSS) attack against a user of the interface. The vulnerability exists because the web UI does not properly validate user-supplied input. 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 affected interface or access sensitive browser-based information.

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 cross-site scripting (XSS) vulnerability exists in the web UI of Cisco Unified Communications Manager and Unified CM Session Management Edition due to improper validation of user-supplied input. An unauthenticated remote attacker can exploit this by tricking users into clicking a crafted malicious link, allowing arbitrary script execution in the user's browser context or access to sensitive browser-based information.

MitigationApply the vendor patch from Cisco for this vulnerability. Until patched, users should avoid clicking untrusted links to the web UI. Implementing proper input validation and output encoding in the web application will remediate the underlying issue.

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\), <= 10.5\(2\)su10>= 11.5\(1\), <= 11.5\(1\)su8= 12.0\(1\)= 12.5\(1\)

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.1/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. Determine the installed Cisco Unified Communications Manager version
    Log into the CUCM server via SSH and run the command 'show version' or 'utils system version' to retrieve the exact version number
    Affected if the version number matches any of the following: 10.5(2) through 10.5(2)su10, 11.5(1) through 11.5(1)su8, 12.0(1), or 12.5(1)
  2. Confirm the CUCM web UI is accessible
    Attempt to access the CUCM administrative web interface at https://<server-ip>/ccmadmin/ or verify the web service is running using 'show web-security' or 'utils service list' commands
    Affected if the web UI is exposed and reachable over the network
  3. Verify the Cisco CDR Analysis and Reporting (CAR) tool web interface status
    Check if the CAR tool web interface is enabled by accessing https://<server-ip>/car/ or reviewing the Cisco Unified Communications Manager service parameters
    Affected if the CAR tool web interface is accessible, as this is a known vector for this XSS vulnerability

You are affected if your installed CUCM version falls within the vulnerable ranges (10.5.2 through 10.5.2su10, 11.5.1 through 11.5.1su8, 12.0.1, or 12.5.1) AND the web UI is accessible to users or attackers.

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
Upgrade available Upgrade to a release after 11.5
Interim mitigation

Apply the vendor patch from Cisco for this vulnerability. Until patched, users should avoid clicking untrusted links to the web UI. Implementing proper input validation and output encoding in the web application will remediate the underlying issue.

Fix this in Unified Communications Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-3346 — 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-2020-3346 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