dbcve.org
Unified Computing System Central SoftwareApplication · Cisco

CVE-2016-1401

MEDIUM · 6.1 CVSS v3.0 Published 2016-05-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/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
Cross-site scripting (XSS) vulnerability in the management interface in Cisco Unified Computing System (UCS) Central Software 1.4(1a) allows remote attackers to inject arbitrary web script or HTML via a crafted value, aka Bug ID CSCuy91250.

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

Stored XSS vulnerability in the web-based management interface of Cisco UCS Central Software allows remote attackers to inject arbitrary JavaScript/HTML through crafted input values. The malicious payload is stored and executed when other users access the affected management interface.

MitigationApply the vendor patch when available. As a temporary measure, restrict access to the management interface to trusted networks only, and implement WAF rules to detect and block XSS attack patterns in HTTP requests.

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 Computing System Central SoftwareApplication
Affected:= 1.4\(1a\)

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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. Verify Cisco UCS Central Software is installed
    Check the system for Cisco UCS Central Software installation. This is typically found on management stations or dedicated UCS Central appliances. Look for the application in installed programs or check the appliance directly.
    Affected if The software is not installed on the system being checked, this CVE does not apply.
  2. Check the installed version of Cisco UCS Central Software
    Access the UCS Central management interface or use the command line interface (CLI) to query the version. From the CLI, use 'show version' or access the web UI and navigate to the About section to confirm the version number.
    Affected if The installed version is exactly 1.4(1a), indicating they are affected by this vulnerability.
  3. Confirm web-based management interface is enabled
    Verify that the UCS Central web-based management interface is accessible and enabled. Check if HTTP/HTTPS management access is configured on the appliance.
    Affected if The web management interface is enabled and accessible - this is required for the stored XSS to be exploitable.
  4. Inspect management interface for suspicious stored scripts
    Review user input fields within the UCS Central web management interface (such as device names, descriptions, or configuration fields) for unexpected script tags or JavaScript code that may have been injected. Check user accounts, device profiles, and configuration pages.
    Affected if Unexpected JavaScript or HTML tags are found stored in management interface fields, indicating potential exploitation.

A system is affected if it runs Cisco UCS Central Software version 1.4(1a) with the web-based management interface enabled, and particularly if suspicious script content is found stored in the management interface.

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 when available. As a temporary measure, restrict access to the management interface to trusted networks only, and implement WAF rules to detect and block XSS attack patterns in HTTP requests.

Fix this in Unified Computing System Central Software Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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