dbcve.org
Unity ConnectionApplication · Cisco

CVE-2017-12212

MEDIUM · 6.1 CVSS v3.0 Published 2017-09-07
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 framework of Cisco Unity Connection could allow an unauthenticated, remote attacker to conduct a reflected cross-site scripting (XSS) attack against a user of the web interface of an affected system. The vulnerability is due to insufficient input validation of certain parameters that are passed to the affected software via the HTTP GET and HTTP POST methods. An attacker who can convince a user to follow an attacker-supplied link could execute arbitrary script or HTML code in the user's browser in the context of an affected site. Known Affected Releases 10.5(2). Cisco Bug IDs: CSCvf25345.

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

Cisco Unity Connection contains a reflected cross-site scripting (XSS) vulnerability in its web framework. The vulnerability stems from insufficient input validation of parameters passed via HTTP GET and POST methods. An unauthenticated remote attacker can exploit this by tricking a user into clicking a malicious link, allowing arbitrary script or HTML execution in the user's browser context.

MitigationApply the Cisco patch for CSCvf25345 when available, or implement input validation/sanitization on all user-supplied parameters in the web interface to neutralize XSS vectors.

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
Unity ConnectionApplication
Affected:= 10.5\(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
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. Identify Cisco Unity Connection version
    Access the Unity Connection admin interface and navigate to About or System Settings, or use the CLI command 'show version' on the underlying platform to determine the installed Unity Connection version
    Affected if The installed version is exactly 10.5(2)
  2. Confirm web framework is enabled
    Verify that the Unity Connection web interface (CUC web admin or Unity Connection Inbox) is accessible and enabled by attempting to reach the standard web URLs such as https://<server>/cucadmin or checking via the CLI command 'show cuc web interface status'
    Affected if The web interface is accessible and exposed to network traffic
  3. Check for recent HTTP access logs
    Review Cisco Unity Connection HTTP access logs (typically found in /var/log/httpx or via the RTMT tool) for suspicious request patterns with script tags or encoded characters in URL parameters
    Affected if Malicious XSS payloads are present in access logs indicating exploitation attempts
  4. Verify web input validation status
    Inspect the web server configuration or proxy logs for user-supplied parameters in GET/POST requests that are not being sanitized - look for parameters that echo back user input without encoding in HTTP responses
    Affected if User-supplied parameters are reflected in responses without proper HTML encoding

You are affected if you are running Cisco Unity Connection version 10.5(2) and have the web interface enabled, as the XSS vulnerability requires both the specific version and an exposed web framework to be exploitable.

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 Cisco patch for CSCvf25345 when available, or implement input validation/sanitization on all user-supplied parameters in the web interface to neutralize XSS vectors.

Fix this in Unity Connection Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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