dbcve.org
Unified Computing System Infrastructure And Unified Computing System SoftwareOperating system · Cisco

CVE-2013-1185

HIGH · 9.3 CVSS v2.0 Published 2013-04-25
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
The web interface in the Manager component in Cisco Unified Computing System (UCS) 1.x and 2.x before 2.0(2m) allows remote attackers to obtain sensitive information by reading a (1) technical-support bundle file or (2) on-device configuration backup, aka Bug ID CSCtq86543.

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

Information disclosure vulnerability in Cisco UCS Manager web interface allows unauthenticated remote attackers to access technical support bundles and on-device configuration backups, which may contain sensitive system information, credentials, or configuration details.

MitigationUpgrade Cisco UCS Manager to version 2.0(2m) or later. As a compensating control, 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 Infrastructure And Unified Computing System SoftwareOperating system
Affected:= 1.0= 1.0\(2k\)= 1.1= 1.1\(1m\)= 1.2= 1.2\(1\)= 1.2\(1a\)= 1.2\(1d\)= 1.3\(1c\)= 1.3\(1m\)= 1.3\(1n\)= 1.3\(1o\)
Unified Computing System 6120xp Fabric InterconnectHardware / appliance
Affected:all versions
Unified Computing System 6140xp Fabric InterconnectHardware / appliance
Affected:all versions
Unified Computing System 6248up Fabric InterconnectHardware / appliance
Affected:all versions
Unified Computing System 6296up Fabric InterconnectHardware / appliance
Affected:all versions
Unified Computing System Integrated Management ControllerHardware / appliance
Affected:all versions

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

AV:N/AC:M/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 Manager is in use
    Access the UCS Manager CLI or web interface via the management IP. Run 'show version' in the CLI or check the About page in the web UI to verify this is a Cisco UCS Manager installation.
    Affected if This is not a Cisco UCS Manager environment
  2. Determine UCS Manager software version
    In the UCS Manager CLI, run 'show version' and note the software version number displayed. Alternatively, access the web interface and navigate to the About or Admin section to view the version.
    Affected if Version is 1.0, 1.0(2k), 1.1, 1.1(1m), 1.2, 1.2(1), 1.2(1a), 1.2(1d), 1.3(1c), 1.3(1m), 1.3(1n), or 1.3(1o)
  3. Identify Fabric Interconnect or IMC model
    Run 'show inventory' in the UCS Manager CLI or check the physical equipment labels. Identify whether the hardware is a 6120xp, 6140xp, 6248up, or 6296xp Fabric Interconnect, or an Integrated Management Controller.
    Affected if Hardware model is any 6120xp, 6140xp, 6248up, 6296up, or Integrated Management Controller regardless of version
  4. Verify web interface network exposure
    Confirm the UCS Manager web interface is reachable over the network. Attempt to access the management interface IP via HTTP/HTTPS from a non-trusted network segment.
    Affected if The web interface is accessible from untrusted network segments
  5. Test for unauthensitive bundle access
    Attempt to access the technical support bundle or configuration backup download endpoints on the web interface without providing any credentials. These are typically found under Support or Admin menus.
    Affected if Technical support bundles or configuration backups can be downloaded without authentication

The environment is affected if running UCS Manager versions 1.0 through 1.3(1o), or using any 6120xp/6140xp/6248up/6296up Fabric Interconnect or Integrated Management Controller, and the web 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

Upgrade Cisco UCS Manager to version 2.0(2m) or later. As a compensating control, restrict network access to the management interface to trusted IP addresses only.

Recommended fix High confidence

Cisco UCS Manager version 2.0(2m) or later

  1. 1. Identify the current Cisco UCS version by accessing the UCS Manager web interface or CLI
  2. 2. Confirm the current version is 1.x or 2.x prior to 2.0(2m)
  3. 3. Review Cisco UCS upgrade documentation and release notes for version 2.0(2m) or later
  4. 4. Schedule a maintenance window as upgrades may require downtime
  5. 5. Back up the current UCS configuration before performing the upgrade
  6. 6. Download the appropriate Cisco UCS software version 2.0(2m) or later from Cisco.com
  7. 7. Follow Cisco's documented upgrade procedure for UCS Manager
  8. 8. After upgrade, verify the UCS Manager version reflects 2.0(2m) or later
Caveat Major version upgrades in UCS may require careful planning; some features or compatibility may change; review release notes for any configuration or compatibility notices

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

Fix this in Unified Computing System Infrastructure And Unified Computing System Software Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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