Unified Contact Center Express Editor SoftwareApplication · Cisco

CVE-2014-0745

MEDIUM · 6.8 CVSS v2.0 Published 2014-02-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/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
Cross-site request forgery (CSRF) vulnerability in the Unified Serviceability subsystem in Cisco Unified Contact Center Express (Unified CCX) allows remote attackers to hijack the authentication of arbitrary users, aka Bug ID CSCum95502.

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

Cross-site request forgery (CSRF) vulnerability in the Unified Serviceability subsystem of Cisco Unified Contact Center Express allows remote attackers to hijack the authentication of arbitrary users by tricking authenticated users into unknowingly submitting malicious requests to the web interface.

MitigationApply the vendor patch for CSCum95502; implement anti-CSRF token validation and Origin/Referer header checks in the Unified Serviceability web application.

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 Express Editor SoftwareApplication
Affected:all versions

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
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/Au:N/C:P/I:P/A:P

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 Contact Center Express is installed
    Check for Cisco UCCX installation by reviewing installed software on the server, looking for 'Cisco Unified Contact Center Express' or 'UCCX' in program listings or running 'dpkg -l | grep -i cisco' on Linux systems
    Affected if The software is present on the system
  2. Identify the UCCX version
    Access the Cisco UCCX administration interface or check version via command line: 'show version' in the UCCX CLI or review the installed package version through the system package manager
    Affected if The installed version is any version of Cisco Unified Contact Center Express Editor Software (all versions are affected)
  3. Determine if Unified Serviceability web interface is enabled
    Access the Unified Serviceability web portal by navigating to the Cisco UCCX web interface (typically https://servername:8443/uccx/serviceability) or check the service status via the UCCX Serviceability page
    Affected if The Unified Serviceability web interface is accessible and enabled on the system
  4. Verify CSRF protection is implemented
    Inspect the web application requests in the Unified Serviceability interface using browser developer tools. Check if the application includes anti-CSRF tokens in forms and validates Origin or Referer headers by examining HTTP request/response headers
    Affected if No anti-CSRF tokens are present in web forms and no Origin/Referer header validation is performed by the application

The environment is affected if Cisco Unified Contact Center Express with the Unified Serviceability web interface is running and lacks anti-CSRF token validation or Origin/Referer header checks.

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 for CSCum95502; implement anti-CSRF token validation and Origin/Referer header checks in the Unified Serviceability web application.

Fix this in Unified Contact Center Express Editor Software Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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