dbcve.org
Unified Intelligence CenterApplication · Cisco

CVE-2024-20325

HIGH · 7.1 CVSS v3.1 Published 2024-02-21
Fix available
A fix is available. Upgrade to 12.5 / 12.6 or later.
See remediation →
73/100
Remediation priority · Elevated
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 Live Data server of Cisco Unified Intelligence Center could allow an unauthenticated, local attacker to read and modify data in a repository that belongs to an internal service on an affected device. This vulnerability is due to insufficient access control implementations on cluster configuration CLI requests. An attacker could exploit this vulnerability by sending a cluster configuration CLI request to specific directories on an affected device. A successful exploit could allow the attacker to read and modify data that is handled by an internal service on the 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

A local unauthenticated attacker can exploit insufficient access control in the Cisco Unified Intelligence Center Live Data server by sending cluster configuration CLI requests to specific directories, allowing unauthorized read and modification of internal service data repositories.

MitigationApply the vendor patch from Cisco when available; until then, restrict local access to the affected device and monitor for suspicious CLI request patterns to specific directories.

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 Intelligence CenterApplication
Affected:< 12.5(1)_es03>= 12.6(1), < 12.6(1)_es08>= 12.6(2), < 12.6(2)ES02

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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 the installed Cisco Unified Intelligence Center version
    Log into the Cisco Unified Intelligence Center CLI or web interface and run the command 'show version' or navigate to the About page in the administration console to retrieve the exact version number
    Affected if The installed version is less than 12.5(1)_es03, or is 12.6(1) but less than 12.6(1)_es08, or is 12.6(2) but less than 12.6(2)ES02
  2. Confirm the Live Data server component is enabled
    Access the Cisco Unified Intelligence Center administration interface and navigate to the Live Data server configuration settings to verify if the Live Data service is currently active
    Affected if The Live Data server is enabled and running in the environment
  3. Review system logs for unauthorized cluster configuration CLI requests
    Examine the Live Data server logs and system audit logs for CLI commands sent to cluster configuration directories, looking for requests from unauthenticated or unexpected sources
    Affected if Log entries show cluster configuration CLI requests to specific directories that were not initiated by authorized administrators
  4. Inspect internal service data repository integrity
    Compare current configuration files and data repositories in the Live Data server directory structure against known good baseline configurations
    Affected if Configuration files or data repositories in the Live Data server directories show unauthorized modifications or unexpected data entries
  5. Verify access control configurations on Live Data server directories
    Review the file system permissions and access control lists on the Live Data server directories that handle cluster configuration requests
    Affected if The directories accepting cluster configuration CLI requests lack proper authentication or authorization controls

Your environment is affected if Cisco Unified Intelligence Center is running a version that falls within the affected ranges AND the Live Data server component is enabled, allowing potential unauthorized access to internal service data repositories.

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.5 / 12.6 or later
Fixed in 12.512.6
Interim mitigation

Apply the vendor patch from Cisco when available; until then, restrict local access to the affected device and monitor for suspicious CLI request patterns to specific directories.

Recommended fix Moderate confidence

12.5(1)_es03, 12.6(1)_es08, or 12.6(2)ES02 (or later releases within your major version branch)

  1. 1. Identify the current version of Cisco Unified Intelligence Center by accessing the administration interface or using the CLI command 'show version'
  2. 2. Based on the current version, determine the appropriate fixed release: for 12.5.x upgrade to 12.5(1)_es03 or later; for 12.6(1) upgrade to 12.6(1)_es08 or later; for 12.6(2) upgrade to 12.6(2)ES02 or later
  3. 3. Review Cisco Unified Intelligence Center upgrade documentation for prerequisites including disk space, backup requirements, and compatibility checks
  4. 4. Create a complete backup of the current configuration and data
  5. 5. Schedule a maintenance window as the upgrade may require downtime
  6. 6. Download the appropriate ES (Emergency Solution) release from Cisco.com software download page
  7. 7. Follow Cisco's standard upgrade procedure - typically via the CLI 'install' command or admin web interface
  8. 8. After upgrade, verify the new version is running using 'show version'

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

Fix this in Unified Intelligence Center Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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