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

CVE-2013-1184

HIGH · 7.8 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 →
87/100
Remediation priority · High
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 management API in the XML API management service in the Manager component in Cisco Unified Computing System (UCS) 1.x before 1.2(1b) allows remote attackers to cause a denial of service (service outage) via a malformed request, aka Bug ID CSCtg48206.

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

The vulnerability exists in the XML API management service within the Cisco UCS Manager component. Remote attackers can send malformed requests to the management API, causing a denial of service that results in a service outage. This affects Cisco UCS Manager versions 1.x prior to version 1.2(1b).

MitigationUpgrade Cisco UCS Manager to version 1.2(1b) or later to remediate this vulnerability. If immediate upgrade is not feasible, consider network segmentation to limit exposure of the management interface to untrusted networks.

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

AV:N/AC:L/Au:N/C:N/I:N/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. Identify the Cisco UCS Manager version
    Access the UCS Manager CLI or GUI and run 'show version' or check the firmware version in the UCS Manager interface. The version is displayed as 1.x or 1.x(y)
    Affected if Version is 1.0, 1.0(2k), 1.1, 1.1(1m), 1.2, 1.2(1), or 1.2(1a) - versions prior to 1.2(1b)
  2. Identify the Fabric Interconnect model
    Check the hardware model number on the physical device or via UCS Manager inventory: 'show inventory' in UCS CLI
    Affected if Model is 6120xp, 6140xp, 6248up, or 6296up Fabric Interconnect (all versions are affected)
  3. Identify the Integrated Management Controller
    Check if the system uses Cisco IMC (Integrated Management Controller) - verify via 'show server health' or check the management interface IP access
    Affected if System uses Integrated Management Controller (all versions affected)
  4. Verify the XML API service is accessible
    Test connectivity to port 443/80 on the UCS Manager management IP address using a tool like curl or by checking if the XML API endpoint responds
    Affected if The XML API management service is exposed and reachable on the network

Your environment is affected if you run Cisco UCS Manager version 1.x prior to 1.2(1b), or use any version of the 6120xp/6140xp/6248up/6296up Fabric Interconnect or Integrated Management Controller with the XML API service 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Cisco UCS Manager to version 1.2(1b) or later to remediate this vulnerability. If immediate upgrade is not feasible, consider network segmentation to limit exposure of the management interface to untrusted networks.

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-1184 — 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-1184 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