Nx OsOperating system · Cisco
CVE-2015-4301
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 · uneditedCisco NX-OS on Nexus 9000 devices 11.1(1c) allows remote authenticated users to cause a denial of service (device hang) via large files that are copied to a device's filesystem, aka Bug ID CSCuu77225.
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 confidenceCisco NX-OS 11.1(1c) on Nexus 9000 switches contains a denial-of-service vulnerability where authenticated remote users copying large files to the device's filesystem can cause the device to hang. The vulnerability is triggered by insufficient handling of large file operations in the NX-OS filesystem subsystem.
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
= 11.1\(1c\)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
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:L/Au:S/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.
-
Verify NX-OS versionRun 'show version' or 'show version | include NX-OS' and locate the displayed NX-OS version stringAffected if The displayed version is exactly 11.1(1c)
-
Confirm Nexus 9000 hardwareRun 'show inventory' or 'show module' and check the model identifier in the outputAffected if The hardware model indicates a Nexus 9000 series switch (such as N9K-C9312PC, N9K-C9508, N9K-9372PX, etc.)
-
Check if file transfer services are enabledRun 'show running-config | include feature scp' or 'show running-config | include feature sftp' to see if SCP or SFTP server features are enabledAffected if SCP or SFTP file transfer services are enabled on the device
-
Verify remote authentication accessRun 'show running-config | include aaa' to check if remote AAA authentication (such as RADIUS or TACACS+) is configured, or check vty line configuration with 'show line'Affected if Remote authentication is enabled allowing authenticated remote users to access the device
-
Check file copy capability for remote usersRun 'show privilege' after logging in as a remote user, or review the role assignments with 'show role' to determine if the authenticated user has file operation privilegesAffected if The authenticated remote user role permits copy or file transfer operations to the device filesystem
The device is affected if it is running NX-OS exactly version 11.1(1c) on Nexus 9000 hardware, and both remote authentication and file transfer services are enabled, allowing authenticated remote users to copy files to the device.
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 to a Cisco NX-OS version that addresses CSCuu77225. If immediate patching is not feasible, restrict filesystem write access to only trusted administrative accounts and implement file size limits on file transfers to mitigate the DoS vector.
Fix this in Nx Os
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-4301 — 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-2015-4301 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