Unified Contact Center ExpressApplication · Cisco

CVE-2019-12633

HIGH · 7.5 CVSS v3.1 Published 2019-09-05
Fix available
A fix is available. Upgrade to 11.6 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 Cisco Unified Contact Center Express (Unified CCX) could allow an unauthenticated, remote attacker to bypass access controls and conduct a server-side request forgery (SSRF) attack on a targeted system. The vulnerability is due to improper validation of user-supplied input on the affected system. An attacker could exploit this vulnerability by sending the user of the web application a crafted request. If the request is processed, the attacker could access the system and perform unauthorized actions.

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 · moderate confidence

Cisco Unified CCX contains an SSRF vulnerability where improper validation of user-supplied input allows unauthenticated remote attackers to bypass access controls. The attacker sends a crafted request to a web application user, and if processed, the attacker can access the system and perform unauthorized actions.

MitigationApply Cisco-provided patches for CVE-2019-12633 and implement proper input validation on user-supplied URLs/requests to prevent server-side request forgery.

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.6\(2\)es04= 12.0\(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
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 Unified CCX installation
    Locate the Cisco Unified CCX server and confirm the product is deployed. Check for processes related to 'CCX' or review installed software on the system.
    Affected if Cisco Unified Contact Center Express is not installed on the system.
  2. Determine the installed CCX version
    Access the Cisco Unified CCX administration interface or use the CLI command 'utils system version' to retrieve the exact version number.
    Affected if The installed version is less than 11.6(2)es04, or is exactly 12.0(1).
  3. Verify web interface accessibility
    Confirm whether the Cisco Unified CCX web interface (typically on port 8443 or 443) is accessible from network locations where untrusted users could send requests.
    Affected if The web interface is exposed to untrusted networks without proper network segmentation.
  4. Check for suspicious web request logs
    Review web server access logs for the CCX application for unusual or crafted URL requests, especially those containing internal IP addresses or non-standard URIs that may indicate SSRF probing.
    Affected if Logs show requests to internal resources or unusual URLs that were not initiated by legitimate users.

A system is affected if Cisco Unified CCX is installed with a version less than 11.6(2)es04 or exactly version 12.0(1), and the web interface is accessible to potential 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 11.6 or later
Fixed in 11.6
Interim mitigation

Apply Cisco-provided patches for CVE-2019-12633 and implement proper input validation on user-supplied URLs/requests to prevent server-side request forgery.

Fix this in Unified Contact Center Express Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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