dbcve.org
Nx OsOperating system · Cisco

CVE-2013-1122

MEDIUM · 5.0 CVSS v2.0 Published 2013-02-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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 the Nexus 7000, when a certain Overlay Transport Virtualization (OTV) configuration is used, allows remote attackers to cause a denial of service (M1-Series module reload) via crafted packets, aka Bug ID CSCud15673.

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 · moderate confidence

Cisco NX-OS on Nexus 7000 switches contains a denial of service vulnerability in the Overlay Transport Virtualization (OTV) feature. When OTV is configured in a specific manner, remote attackers can send crafted packets to cause the M1-Series module to reload, resulting in service disruption.

MitigationApply Cisco patches when available; review OTV configuration to understand the vulnerable state and implement compensating controls such as ACLs to limit exposure to untrusted networks until a fix is deployed.

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:all versions= 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\)
Nexus 7000Hardware / 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
Partial

AV:N/AC:L/Au:N/C:N/I:N/A:P

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 module' to confirm the hardware is a Cisco Nexus 7000 series switch
    Affected if The device model is not a Cisco Nexus 7000 series switch (the vulnerability only affects Nexus 7000)
  2. Confirm NX-OS is running
    Run 'show version' to verify the operating system is Cisco NX-OS
    Affected if The device is not running Cisco NX-OS (this vulnerability is specific to NX-OS)
  3. Verify OTV feature is enabled
    Run 'show feature | include otv' to check if Overlay Transport Virtualization is enabled
    Affected if OTV feature is not enabled (the vulnerability requires OTV to be active)
  4. Inspect OTV configuration
    Run 'show running-config | include otv' or 'show otv' to examine the OTV configuration details
    Affected if OTV is configured in a manner that exposes the vulnerability (the specific configuration pattern that enables the attack vector)
  5. Check for recent unexpected module reloads
    Run 'show logging' or 'show module' to review system logs for M1-Series module reload events
    Affected if The M1-Series module has reloaded unexpectedly without an administrative cause (indicates the vulnerability may have been exploited)

You are affected if you have a Nexus 7000 switch running NX-OS with OTV feature enabled and configured in the vulnerable manner.

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 Cisco patches when available; review OTV configuration to understand the vulnerable state and implement compensating controls such as ACLs to limit exposure to untrusted networks until a fix is deployed.

Fix this in Nx Os 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-1122 — 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-1122 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