dbcve.org
Unified Contact Center ExpressApplication · Cisco

CVE-2017-6722

MEDIUM · 6.1 CVSS v3.0 Published 2017-07-04
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 Extensible Messaging and Presence Protocol (XMPP) service of Cisco Unified Contact Center Express (UCCx) could allow an unauthenticated, remote attacker to masquerade as a legitimate user, aka a Clear Text Authentication Vulnerability. More Information: CSCuw86638. Known Affected Releases: 10.6(1). Known Fixed Releases: 11.5(1.10000.61).

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

The vulnerability exists in the XMPP (Extensible Messaging and Presence Protocol) service of Cisco Unified Contact Center Express. It allows an unauthenticated, remote attacker to transmit clear text authentication credentials, enabling them to masquerade as legitimate users and potentially gain unauthorized access to the contact center system.

MitigationUpgrade Cisco UCCx to version 11.5(1.10000.61) or later to remediate this vulnerability. If immediate patching is not possible, restrict network access to the XMPP service from untrusted networks using firewalls or ACLs.

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 Contact Center ExpressApplication
Affected:= 11.5\(1\)= 11.5.1es01= 11.5.1su1

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 the installed Cisco UCCx version
    Access the Cisco Unified Contact Center Express administration interface or check the version via command line using 'show version' or similar system commands. Alternatively, check the About page in the UCCx GUI.
    Affected if The installed version matches exactly 11.5(1), 11.5.1es01, or 11.5.1su1 (these are the affected versions). Compare your version against these specific strings.
  2. Verify XMPP service status
    Log into the Cisco UCCx server and check if the XMPP (Cisco XMPP Messaging Service) is enabled and running. This can be done via the Serviceability page in UCCx or by checking running services on the underlying operating system.
    Affected if The XMPP service is enabled and listening on the network, making it reachable for remote exploitation.
  3. Inspect XMPP service configuration
    Access the XMPP service configuration through the UCCx Administration interface under the XMPP settings. Look for authentication-related parameters, particularly those governing how credentials are transmitted (e.g., check for SASL mechanisms, TLS settings, or lack thereof).
    Affected if The XMPP service is configured to allow clear text authentication (plain auth) or has TLS disabled, which would permit transmission of credentials in clear text.

A user is affected if their Cisco UCCx version is exactly 11.5(1), 11.5.1es01, or 11.5.1su1 AND the XMPP service is enabled with clear text authentication allowed.

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

Upgrade Cisco UCCx to version 11.5(1.10000.61) or later to remediate this vulnerability. If immediate patching is not possible, restrict network access to the XMPP service from untrusted networks using firewalls or ACLs.

Fix this in Unified Contact Center Express Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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