dbcve.org
Nx OsOperating system · Cisco

CVE-2013-1179

HIGH · 9.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 →
96/100
Remediation priority · Urgent
Remotely reachable 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
Multiple buffer overflows in the (1) SNMP and (2) License Manager implementations in Cisco NX-OS on Nexus 7000 devices 4.x and 5.x before 5.2(5) and 6.x before 6.1(1) and MDS 9000 devices 4.x and 5.x before 5.2(5) allow remote authenticated users to execute arbitrary code via a crafted SNMP request, aka Bug ID CSCtx54830.

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 vulnerabilities in the SNMP and License Manager implementations in Cisco NX-OS on Nexus 7000 and MDS 9000 devices allow remote authenticated users to execute arbitrary code via crafted SNMP requests. The vulnerabilities affect specific version ranges of NX-OS (4.x, 5.x before 5.2(5), 6.x before 6.1(1)) on both platforms.

MitigationApply Cisco patches per the advisory (upgrade to 5.2(5) or later for 4.x/5.x, 6.1(1) or later for 6.x). As immediate workarounds, restrict SNMP access to trusted management networks and limit the number of authenticated users with SNMP access.

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 7000Hardware / appliance
Affected:all versions
Nexus 7000 10 SlotHardware / appliance
Affected:all versions
Nexus 7000 18 SlotHardware / appliance
Affected:all versions
Nexus 7000 9 SlotHardware / appliance
Affected:all versions
Mds 9000Hardware / 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
Single
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:S/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 the device model
    Run 'show version' or 'show inventory' to confirm the hardware model is Cisco Nexus 7000 series or MDS 9000 series
    Affected if Device is a Nexus 7000 (any slot configuration) or MDS 9000 switch
  2. Determine the NX-OS version
    Run 'show version' and locate the 'NX-OS' or 'system' version line. Compare the full version number against the affected ranges: any 4.x version, 5.x versions before 5.2(5), or 6.x versions before 6.1(1)
    Affected if NX-OS version is 4.x, 5.x before 5.2(5), or 6.x before 6.1(1)
  3. Verify SNMP is enabled
    Run 'show snmp' to check if SNMP is configured and enabled on the device
    Affected if SNMP is enabled and accessible to the attacker
  4. Check SNMP community or user configuration
    Run 'show snmp community' and 'show snmp user' to see configured SNMP communities and users. The vulnerability requires authenticated SNMP access
    Affected if SNMP community strings or users are configured, allowing authenticated remote access

A user is affected if they run a Nexus 7000 or MDS 9000 device with NX-OS versions 4.x, 5.x before 5.2(5), or 6.x before 6.1(1), and have SNMP enabled with authentication configured for remote access.

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

Apply Cisco patches per the advisory (upgrade to 5.2(5) or later for 4.x/5.x, 6.1(1) or later for 6.x). As immediate workarounds, restrict SNMP access to trusted management networks and limit the number of authenticated users with SNMP access.

Recommended fix High confidence

NX-OS 5.2(5) or later for 5.x versions; NX-OS 6.1(1) or later for 6.x versions; or latest stable release supported by hardware

  1. Identify the specific device model (Nexus 7000 series or MDS 9000)
  2. Check current NX-OS version using 'show version' command
  3. For Nexus 7000: If running 5.x, upgrade to NX-OS 5.2(5) or later. If running 6.x, upgrade to NX-OS 6.1(1) or later
  4. For MDS 9000: Upgrade to NX-OS 5.2(5) or later
  5. Schedule maintenance window as upgrade requires reboot
  6. Back up current configuration before upgrade
  7. Upload new NX-OS image to device bootflash
  8. Configure boot variable to point to new image using 'boot system' command
Caveat Upgrade requires device reload causing downtime; verify hardware compatibility with target NX-OS version before upgrading

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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