dbcve.org
Nx OsOperating system · Cisco

CVE-2013-1181

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
Cisco NX-OS on Nexus 5500 devices 4.x and 5.x before 5.0(3)N2(2), Nexus 3000 devices 5.x before 5.0(3)U3(2), and Unified Computing System (UCS) 6200 devices before 2.0(1w) allows remote attackers to cause a denial of service (device reload) by sending a jumbo packet to the management interface, aka Bug IDs CSCtx17544, CSCts10593, and CSCtx95389.

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

This is a denial of service vulnerability in Cisco NX-OS software on Nexus 5500, Nexus 3000, and UCS 6200 devices. Attackers can trigger an uncontrolled device reload by sending a jumbo packet (packet exceeding standard MTU) to the management interface, causing the affected device to crash and restart.

MitigationApply the vendor-supplied patches: upgrade Nexus 5500 to 5.0(3)N2(2) or later, Nexus 3000 to 5.0(3)U3(2) or later, and UCS 6200 to 2.0(1w) or later. Additionally, restrict access to the management interface via network segmentation or ACLs to limit exposure 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
Nx OsOperating system
Affected:= 4.0= 4.0\(0\)n1\(1a\)= 4.0\(0\)n1\(2\)= 4.0\(0\)n1\(2a\)= 4.0\(1a\)n1\(1\)= 4.0\(1a\)n1\(1a\)= 4.0\(1a\)n2\(1\)= 4.0\(1a\)n2\(1a\)= 4.0\(4\)sv1\(1\)= 4.0\(4\)sv1\(2\)= 4.0\(4\)sv1\(3\)= 4.0\(4\)sv1\(3a\)
Nexus 5548pHardware / appliance
Affected:all versions
Nexus 5548upHardware / appliance
Affected:all versions
Nexus 5596upHardware / appliance
Affected:all versions
Nexus 3016qHardware / appliance
Affected:all versions
Nexus 3048Hardware / appliance
Affected:all versions
Nexus 3064tHardware / appliance
Affected:all versions
Nexus 3064xHardware / 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 device model
    Run 'show inventory' or 'show version' on the device CLI to confirm the hardware model
    Affected if The model is Nexus 5548p, Nexus 5548up, Nexus 5596up, Nexus 3016q, Nexus 3048, Nexus 3064t, or Nexus 3064x
  2. Check the NX-OS version
    Run 'show version' to obtain the software version number
    Affected if The version is 4.0(0)n1(1a), 4.0(0)n1(2), 4.0(0)n1(2a), 4.0(1a)n1(1), 4.0(1a)n1(1a), 4.0(1a)n2(1), 4.0(1a)n2(1a), 4.0(4)sv1(1), 4.0(4)sv1(2), 4.0(4)sv1(3), or 4.0(4)sv1(3a) - or if the device is one of the all-versions models regardless of version
  3. Verify management interface status
    Run 'show interface mgmt0' to confirm the management interface is configured and up
    Affected if The management interface exists and is in an up state, making it reachable for an attack
  4. Confirm management interface network exposure
    Review the network configuration to determine if the management interface is reachable from untrusted networks - check VLAN assignments, ACLs applied to mgmt0, and routing table entries for the management interface
    Affected if The management interface has an IP address in a subnet accessible from untrusted networks or lacks restrictive ACLs

The environment is affected if the device is a Nexus 5500 or Nexus 3000 model running an affected NX-OS version AND the management interface is reachable from untrusted networks.

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

Apply the vendor-supplied patches: upgrade Nexus 5500 to 5.0(3)N2(2) or later, Nexus 3000 to 5.0(3)U3(2) or later, and UCS 6200 to 2.0(1w) or later. Additionally, restrict access to the management interface via network segmentation or ACLs to limit exposure to untrusted networks.

Fix this in Nx Os Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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