dbcve.org
Unified Computing System Central SoftwareApplication · Cisco

CVE-2015-0701

HIGH · 10.0 CVSS v2.0 Published 2015-05-07
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 UCS Central Software before 1.3(1a) allows remote attackers to execute arbitrary commands via a crafted HTTP request, aka Bug ID CSCut46961.

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

Cisco UCS Central Software versions prior to 1.3(1a) contain a command injection vulnerability in the HTTP interface allowing unauthenticated remote attackers to execute arbitrary operating system commands. The CVSS 10 score reflects the critical severity of unauthenticated remote code execution capability.

MitigationUpgrade to Cisco UCS Central Software version 1.3(1a) or later. If immediate patching is not feasible, restrict network access to the management interface to trusted IP addresses only.

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.0_base= 1.1_base= 1.2\(1a\)= 1.2\(1d\)= 1.2\(1e\)= 1.2\(1f\)

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 UCS Central is deployed
    Identify whether Cisco UCS Central Software is running in your environment. This is typically a virtual appliance or physical appliance used for centralized management of UCS infrastructure.
    Affected if Cisco UCS Central Software is installed and running
  2. Retrieve the installed version
    Access the system administration interface (CLI, GUI, or API) and obtain the software version number. In the CLI this is typically done with the 'show version' command or by viewing the About section in the web interface.
    Affected if Version cannot be determined or the system is unreachable
  3. Compare against affected versions
    Compare your installed version against the vulnerable list: 1.0_base, 1.1_base, 1.2(1a), 1.2(1d), 1.2(1e), 1.2(1f). Any of these versions are affected.
    Affected if Installed version matches any of: 1.0_base, 1.1_base, 1.2(1a), 1.2(1d), 1.2(1e), or 1.2(1f)
  4. Verify HTTP management interface exposure
    Determine if the HTTP management interface is network-accessible. The vulnerability is exploitable through the HTTP interface, so check whether port 80/443 or the management IP is exposed to untrusted networks.
    Affected if HTTP management interface is accessible from untrusted networks (not restricted to trusted IPs)

You are affected if Cisco UCS Central Software is running and the installed version is 1.0_base, 1.1_base, 1.2(1a), 1.2(1d), 1.2(1e), or 1.2(1f) with the HTTP interface 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

Upgrade to Cisco UCS Central Software version 1.3(1a) or later. If immediate patching is not feasible, restrict network access to the management interface to trusted IP addresses only.

Recommended fix High confidence

Cisco UCS Central Software 1.3(1a) or later

  1. Verify current Cisco UCS Central Software version by accessing the admin console or using 'show version' command
  2. Download Cisco UCS Central Software version 1.3(1a) or later from Cisco's official download page
  3. Review Cisco UCS Central upgrade documentation for your specific deployment model
  4. Schedule maintenance window as upgrade may require downtime
  5. Back up current UCS Central configuration before proceeding
  6. Upload the new software image to the UCS Central management interface
  7. Follow Cisco's documented upgrade procedure to install version 1.3(1a) or later
  8. Verify successful installation by confirming new version with 'show version' command
Caveat Review Cisco release notes for 1.3(1a) for any changes in functionality or configuration requirements before upgrading

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
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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