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

CVE-2013-1183

HIGH · 10.0 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
Buffer overflow in the Intelligent Platform Management Interface (IPMI) functionality in the Manager component in Cisco Unified Computing System (UCS) 1.0 and 1.1 before 1.1(1j) and 1.2 before 1.2(1b) allows remote attackers to execute arbitrary code via malformed data in a UDP packet, aka Bug ID CSCtd32371.

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

Buffer overflow vulnerability in the IPMI (Intelligent Platform Management Interface) Manager component of Cisco Unified Computing System (UCS) versions 1.0, 1.1, and 1.2 allows remote attackers to execute arbitrary code via malformed UDP packets. The CVSS 10 score indicates trivial exploitability with no authentication required.

MitigationUpgrade Cisco UCS firmware to version 1.1(1j), 1.2(1b), or later. If patching is not immediately feasible, disable or restrict access to the IPMI interface via network segmentation and firewall rules.

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

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. Identify Cisco UCS firmware version
    Use the Cisco UCS Manager CLI or GUI to retrieve the firmware version. From the UCS Manager > Equipment tab > Controller > BIOS, or run 'show version' in the UCSM CLI.
    Affected if The version matches 1.0, 1.0(2k), 1.1, 1.1(1m), 1.2, 1.2(1), or 1.2(1a)
  2. Identify Fabric Interconnect model
    Check the physical hardware or UCS Manager inventory for the Fabric Interconnect model number.
    Affected if The model is a 6120xp, 6140xp, 6248up, or 6296xp Fabric Interconnect (any version)
  3. Verify IPMI service status
    Check if the IPMI Manager service is enabled on the UCS firmware. In UCS Manager, navigate to Equipment > IPMI or use the 'ipmi status' command in the UCSM CLI.
    Affected if IPMI Manager is enabled and running on the device
  4. Check IPMI network exposure
    Identify if UDP port 623 (standard IPMI port) is open to untrusted networks. Use network scanning tools or review firewall rules and access lists.
    Affected if UDP port 623 is accessible from networks outside the trusted management segment
  5. Confirm management interface configuration
    Review the management VLAN and IP address configuration for the IPMI interface in UCS Manager under Admin > Communication Management > Communication Services.
    Affected if The IPMI interface is configured with an IP address on a shared or production network rather than an isolated management network

You are affected if your Cisco UCS runs firmware version 1.0 through 1.2(1a), or uses a 6120xp/6140xp/6248up/6296up Fabric Interconnect, and the IPMI service is enabled and reachable via UDP port 623.

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 firmware to version 1.1(1j), 1.2(1b), or later. If patching is not immediately feasible, disable or restrict access to the IPMI interface via network segmentation and firewall rules.

Recommended fix High confidence

1.1(1j) or later for 1.0.x/1.1.x branches; 1.2(1b) or later for 1.2.x branch

  1. 1. Identify the current Cisco UCS version by logging into Cisco UCS Manager and checking the version under the General tab or using 'show version' command
  2. 2. For UCS versions 1.0.x or 1.1.x: Plan upgrade to version 1.1(1j) or later
  3. 3. For UCS version 1.2.x: Plan upgrade to version 1.2(1b) or later
  4. 4. Download the appropriate firmware bundle from Cisco.com (requires valid Cisco service contract)
  5. 5. Backup UCS configuration before initiating upgrade
  6. 6. Schedule maintenance window as upgrades require downtime
  7. 7. Follow Cisco UCS upgrade procedure using Cisco UCS Manager or CLI - typically involves uploading firmware to firmware repository and then installing via 'scope firmware' and 'firmware install' commands
  8. 8. Verify upgrade completed successfully and system is running fixed version
Caveat Firmware upgrades may require downtime and could have compatibility implications with connected devices; test in lab environment before production deployment

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
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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