dbcve.org
Unified Intelligence CenterApplication · Cisco

CVE-2019-1860

MEDIUM · 5.9 CVSS v3.0 Published 2019-05-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
66/100
Remediation priority · Elevated
Remotely reachable No privileges

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 dashboard gadget rendering of Cisco Unified Intelligence Center could allow an unauthenticated, remote attacker to obtain or manipulate sensitive information between a user’s browser and Cisco Unified Intelligence Center. The vulnerability is due to the lack of gadget validation. An attacker could exploit this vulnerability by forcing a user to load a malicious gadget. A successful exploit could allow the attacker to obtain sensitive information, such as current user credentials, or manipulate data between the user’s browser and Cisco Unified Intelligence Center in the context of the malicious gadget.

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

The vulnerability exists in Cisco Unified Intelligence Center's dashboard gadget rendering mechanism due to missing validation of gadgets. An unauthenticated remote attacker can force users to load malicious gadgets, enabling theft of sensitive information like user credentials or manipulation of data in the context of the user's session.

MitigationImplement strict validation and sanitization of all gadgets rendered in the dashboard, enforce Content Security Policy (CSP) headers to restrict gadget sources, and apply proper Same-Origin Policy controls to prevent cross-origin gadget injection.

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

CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/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 Intelligence Center installation and version
    Locate the Cisco Unified Intelligence Center installation and determine its installed version number. Compare your version against the affected version: 12.0(1).
    Affected if The installed version is exactly 12.0(1)
  2. Determine if dashboard functionality is accessible
    Verify whether the web interface for Cisco Unified Intelligence Center is accessible and if users can access dashboard features that render gadgets.
    Affected if The dashboard interface is accessible to users or unauthenticated attackers
  3. Inspect gadget source configuration
    Examine the configuration settings related to dashboard gadgets, specifically looking for any controls that define which gadget sources are allowed to be loaded.
    Affected if Gadget sources are not restricted or validated
  4. Check for Content Security Policy headers
    Inspect HTTP responses from the Cisco Unified Intelligence Center web interface to determine if Content Security Policy (CSP) headers are present and whether they restrict gadget sources.
    Affected if CSP headers are missing or do not restrict external gadget sources
  5. Review Same-Origin Policy controls
    Check the server or application configuration for Same-Origin Policy settings that control cross-origin gadget injection.
    Affected if Same-Origin Policy controls are not enforced or can be bypassed

You are affected if Cisco Unified Intelligence Center version 12.0(1) is installed AND the dashboard gadget rendering feature is accessible without proper validation, CSP, or Same-Origin Policy controls in place.

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

Implement strict validation and sanitization of all gadgets rendered in the dashboard, enforce Content Security Policy (CSP) headers to restrict gadget sources, and apply proper Same-Origin Policy controls to prevent cross-origin gadget injection.

Fix this in Unified Intelligence Center Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
34.0 hours of engineering $6,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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