Nx OsOperating system · Cisco
CVE-2014-2201
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 · uneditedThe Message Transfer Service (MTS) in Cisco NX-OS before 6.2(7) on MDS 9000 devices and 6.0 before 6.0(2) on Nexus 7000 devices allows remote attackers to cause a denial of service (NULL pointer dereference and kernel panic) via a large volume of crafted traffic, aka Bug ID CSCtw98915.
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 confidenceThe Message Transfer Service (MTS) in Cisco NX-OS contains a NULL pointer dereference vulnerability when processing a large volume of crafted traffic. On affected MDS 9000 and Nexus 7000 devices running NX-OS versions prior to 6.2(7) and 6.0(2) respectively, this causes kernel panic resulting in complete denial of service.
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
= 6.0\(1\)<= 6.2\(5a\)= 6.2\(1\)= 6.2\(1n\)= 6.2\(3\)= 6.2\(3n\)= 6.2\(5\)
Nexus 7000Hardware / appliance
all versions
Nexus 7000 10 SlotHardware / appliance
all versions
Nexus 7000 18 SlotHardware / appliance
all versions
Nexus 7000 9 SlotHardware / appliance
all versions
Mds 9000Hardware / appliance
all versions
Mds 9100Hardware / appliance
all versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelRun 'show module' or 'show inventory' to confirm the hardware is a Cisco Nexus 7000 series or MDS 9000 series deviceAffected if Device is a Nexus 7000 (any slot variant) or MDS 9000/9100 series switch
-
Check the NX-OS versionRun 'show version' and note the displayed NX-OS release number (e.g., 6.2(5a), 6.0(1))Affected if Version is 6.0(1) through 6.2(5a) for generic NX-OS, or any version for Nexus 7000 and MDS 9000 (listed as 'all versions')
-
Confirm the MTS service is activeRun 'show system internal mts statistics' or check that the system is operational (MTS is a core kernel service that runs by default on NX-OS)Affected if Device is running an affected NX-OS version and the system is operational (MTS cannot be disabled as it is a core system service)
The device is affected if it is a Nexus 7000 or MDS 9000/9100 running any NX-OS version prior to 6.0(2) for Nexus 7000 or prior to 6.2(7) for MDS 9000, or if it falls within the 6.0(1) to 6.2(5a) range listed as affected.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade NX-OS to version 6.2(7) or later for MDS 9000 devices, or 6.0(2) or later for Nexus 7000 devices. If immediate patching is not feasible, restrict network access to these devices using ACLs or network segmentation to limit exposure to untrusted traffic sources.
Fix this in Nx Os
Scoped from the published advisory
- Consultation6.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,048.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2201 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-2201 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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