dbcve.org
Unified Contact Center ExpressApplication · Cisco

CVE-2020-3267

HIGH · 7.1 CVSS v3.1 Published 2020-06-03
Fix available
A fix is available. Upgrade to 12.5 or later.
See remediation →
77/100
Remediation priority · High
Remotely reachable 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 the API subsystem of Cisco Unified Contact Center Express (Unified CCX) could allow an authenticated, remote attacker to change the availability state of any agent. The vulnerability is due to insufficient authorization enforcement on an affected system. An attacker could exploit this vulnerability by authenticating to an affected system with valid agent credentials and performing a specific API call with crafted input. A successful exploit could allow the attacker to change the availability state of an agent, potentially causing a denial of service condition.

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

Insufficient authorization enforcement in the API subsystem of Cisco Unified CCX allows an authenticated attacker with valid agent credentials to change the availability state of ANY agent on the system via a specific API call with crafted input, potentially causing denial of service.

MitigationApply the vendor patch from Cisco for CVE-2020-3267; if immediate patching is not feasible, implement network segmentation to restrict API access and enable detailed API request logging to detect unauthorized availability state changes.

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:< 12.5\(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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H

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 version
    Access the Cisco Unified CCX Administration interface or use the CLI command 'show version' to determine the installed version number.
    Affected if The installed version is below 12.5(1)
  2. Confirm API subsystem is accessible
    Verify that the API subsystem is enabled and reachable. Check if the URL pattern '/crm/api/v1/agents' is accessible from agent workstations or management interfaces.
    Affected if The API endpoint is exposed and accessible without additional authentication beyond agent credentials
  3. Review agent account configuration
    List active agent accounts in the Cisco Unified CCX Administration console under 'Tools' > 'Agent Management' to identify accounts that have API access capabilities.
    Affected if There are active agent accounts with valid credentials that can authenticate to the API subsystem
  4. Examine API request logs
    Access the Cisco Unified CCX Serviceability interface and review API access logs for requests to agent availability modification endpoints, looking for unexpected source accounts changing other agents' states.
    Affected if Logs show API calls from agent accounts modifying availability states of agents other than their own

Your environment is affected if the installed Cisco Unified CCX version is below 12.5(1) and the API subsystem is accessible with agent credentials.

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 12.5 or later
Fixed in 12.5
Interim mitigation

Apply the vendor patch from Cisco for CVE-2020-3267; if immediate patching is not feasible, implement network segmentation to restrict API access and enable detailed API request logging to detect unauthorized availability state changes.

Fix this in Unified Contact Center Express Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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