dbcve.org
Unified Computing System Central SoftwareApplication · Cisco

CVE-2016-1352

CRITICAL · 9.8 CVSS v3.0 Published 2016-04-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Cisco Unified Computing System (UCS) Central Software 1.3(1b) and earlier allows remote attackers to execute arbitrary OS commands via a crafted HTTP request, aka Bug ID CSCuv33856.

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

Command injection vulnerability in Cisco UCS Central Software 1.3(1b) and earlier allows remote unauthenticated attackers to execute arbitrary operating system commands via a crafted HTTP request. This is a pre-authentication flaw, likely due to insufficient input validation allowing shell metacharacters to be passed to underlying system calls.

MitigationApply the vendor patch for Cisco UCS Central Software. If immediate patching is not feasible, restrict network access to the UCS Central management interface to trusted IP addresses only as a compensating control.

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

CVSS:3.0/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. Identify Cisco UCS Central Software installation
    Check if Cisco UCS Central is running on the system. This is typically deployed as a virtual appliance or hardware appliance. Look for the UCS Central management processes or access the management interface.
    Affected if Cisco UCS Central Software is not installed on the system.
  2. Determine the installed software version
    Access the UCS Central management interface or CLI and retrieve the software version. The version is typically displayed in the web GUI header or obtainable via 'show version' command in the CLI.
    Affected if The installed version is 1.3(1b) or any earlier version (such as 1.3(0.1)). Compare your version against these affected ranges.
  3. Verify HTTP management interface accessibility
    Attempt to access the Cisco UCS Central web interface over HTTP (port 80) or HTTPS (port 443) from a network location. Check if the management interface responds to HTTP requests.
    Affected if The HTTP management interface is reachable from the network. This is the attack vector for the command injection.
  4. Check network exposure of management interface
    Review firewall rules, ACLs, or network segmentation settings to determine if the UCS Central management ports (80/443) are exposed to untrusted networks or the public internet.
    Affected if The management interface is exposed to untrusted or external networks without restricted access controls.

You are affected if Cisco UCS Central Software is installed with version 1.3(1b) or earlier and its HTTP management interface is network-accessible.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch for Cisco UCS Central Software. If immediate patching is not feasible, restrict network access to the UCS Central management interface to trusted IP addresses only as a compensating control.

Recommended fix Moderate confidence

Cisco UCS Central Software 1.3(2) or later stable release

  1. 1. Identify current Cisco UCS Central Software version via GUI or CLI (show version)
  2. 2. Access Cisco.com and navigate to the Cisco UCS Central Software download page
  3. 3. Download version 1.3(2) or later from the Cisco UCS Central Software 1.3.x release tree
  4. 4. Plan maintenance window as upgrade requires brief downtime
  5. 5. Back up current UCS Central configuration
  6. 6. Install upgrade via UCS Central GUI (Admin > Software Management) or via UCS Manager CLI
  7. 7. After upgrade, verify new version is running: show version
  8. 8. Validate functionality by testing core UCS Central operations
Caveat Review Cisco release notes for 1.3(2) for any configuration or behavioral changes; some GUI paths or API endpoints may have changed

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

Fix this in Unified Computing System Central Software Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
32.0 hours of engineering $5,520
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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