dbcve.org
Unified Contact Center ExpressApplication · Cisco

CVE-2020-3280

CRITICAL · 9.8 CVSS v3.1 Published 2020-05-22
Fix available
A fix is available. Upgrade to 12.0 or later.
See remediation →
100/100
Remediation priority · Urgent
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 the Java Remote Management Interface of Cisco Unified Contact Center Express (Unified CCX) could allow an unauthenticated, remote attacker to execute arbitrary code on an affected device. The vulnerability is due to insecure deserialization of user-supplied content by the affected software. An attacker could exploit this vulnerability by sending a malicious serialized Java object to a specific listener on an affected system. A successful exploit could allow the attacker to execute arbitrary code as the root user on an affected device.

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

Insecure deserialization vulnerability in the Java Remote Management Interface of Cisco Unified CCX allows unauthenticated remote attackers to send malicious serialized Java objects that execute arbitrary code as root.

MitigationApply the vendor-supplied patch for Cisco Unified CCX to remediate this vulnerability; until patched, restrict network access to the Java RMI listener or disable it if not required.

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.0, < 12.0\(1\)es03

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Confirm Cisco Unified CCX installation
    Identify if Cisco Unified Contact Center Express is deployed in your environment. Check system inventory, documentation, or consult with system administrators to confirm this product is in use.
    Affected if Not applicable - this is a prerequisite check to determine if the product exists in your environment
  2. Check installed version
    Access the Cisco Unified CCX administration interface or use the CLI to retrieve the exact version number. Compare your version against the affected range: 12.0 through 12.0(1)es02. Versions prior to 12.0 and version 12.0(1)es03 and later are not affected.
    Affected if Your installed version falls within 12.0 to 12.0(1)es02 inclusive
  3. Verify Java RMI listener status
    Determine if the Java Remote Management Interface (RMI) service is enabled and running on your Cisco Unified CCX system. This typically involves checking the service configuration via the CCX administration interface or examining active listening ports associated with the RMI service.
    Affected if Java RMI listener is enabled and actively accepting connections
  4. Assess network accessibility of RMI port
    Review firewall rules and network segmentation to determine if the Java RMI listener port is accessible from untrusted networks. This vulnerability can be exploited by unauthenticated remote attackers if the port is exposed.
    Affected if The Java RMI listener port is reachable from networks outside your trusted administrative zone

You are affected if your Cisco Unified CCX version is between 12.0 and 12.0(1)es02 inclusive AND the Java RMI listener is enabled and accessible from your network.

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.

dbcve · scoped
Upgrade available Upgrade to 12.0 or later
Fixed in 12.0
Interim mitigation

Apply the vendor-supplied patch for Cisco Unified CCX to remediate this vulnerability; until patched, restrict network access to the Java RMI listener or disable it if not required.

Recommended fix High confidence

12.0(1)es03 or later

  1. Back up the Unified CCX system and verify data integrity before proceeding with any upgrade
  2. Download the fixed release 12.0(1)es03 or later from the Cisco Software Download center (requires valid Cisco service contract)
  3. Review Cisco Unified CCX upgrade documentation for version-specific upgrade procedures
  4. Apply the upgrade following Cisco's standard upgrade process for Unified CCX 12.x releases
  5. After upgrade completes, verify the Java Remote Management Interface is functioning normally
  6. Confirm the system is running the patched version 12.0(1)es03 or higher
Caveat Review Cisco upgrade documentation for Unified CCX 12.0 for any compatibility considerations, prerequisites, or migration requirements before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Unified Contact Center Express Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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