Unified Communications Domain ManagerApplication · Cisco

CVE-2017-6670

MEDIUM · 6.1 CVSS v3.0 Published 2017-06-13
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 GUI of Cisco Unified Communications Domain Manager could allow an unauthenticated, remote attacker to redirect a user to a malicious web page, aka an Open Redirect issue. More Information: CSCvc54813. Known Affected Releases: 8.1(7)ER1.

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

An open redirect vulnerability in the web-based GUI of Cisco Unified Communications Domain Manager allows unauthenticated remote attackers to craft malicious URLs that redirect victims to attacker-controlled websites by manipulating redirect parameters in the application.

MitigationApply the vendor patch (8.1(7)ER1 or later) when available. If no patch is immediately available, implement URL filtering at the network edge to block suspicious external redirect patterns and monitor for phishing attempts.

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 Domain ManagerApplication
Affected:= 8.1\(7\)er1

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 Domain Manager is installed
    Access the web-based management interface or check system inventory for the presence of Cisco Unified Communications Domain Manager product
    Affected if The product Cisco Unified Communications Domain Manager is running in the environment
  2. Determine the installed version
    Log into the web-based GUI and navigate to the About or System Information page, or use the CLI command 'show version' if SSH access is available, to identify the exact software version
    Affected if The installed version is exactly 8.1(7)er1
  3. Verify the web GUI is accessible
    Attempt to access the management interface via HTTPS/HTTP on the standard management ports (typically 8443 or 443) to confirm the web interface is exposed
    Affected if The web-based GUI is accessible and responds to HTTP/HTTPS requests
  4. Test for open redirect vulnerability (optional)
    Craft a test URL by appending a redirect parameter pointing to an external domain (for example, ?redirect=http://example.com or similar parameter patterns used in the application) and observe if the application allows redirection to the external domain without validation
    Affected if The application redirects to the specified external URL without proper validation, indicating the open redirect vulnerability is present

The environment is affected if Cisco Unified Communications Domain Manager version 8.1(7)er1 is installed and its web-based GUI is accessible, allowing attacker-controlled redirect parameters to function.

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 (8.1(7)ER1 or later) when available. If no patch is immediately available, implement URL filtering at the network edge to block suspicious external redirect patterns and monitor for phishing attempts.

Fix this in Unified Communications Domain Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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 locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-6670 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