CVE-2015-4197
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 5.2(5) on Nexus 7000 devices allows remote attackers to cause a denial of service (device crash) by sending a malformed LLDP packet on the local network, aka Bug ID CSCud89415.
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 confidenceThis is a denial of service vulnerability in Cisco NX-OS version 5.2(5) running on Nexus 7000 series switches. Attackers on the local network can send malformed LLDP (Link Layer Discovery Protocol) packets to trigger a device crash. LLDP is a Layer 2 discovery protocol used for advertising device identity to neighboring devices.
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= 5.2\(5\)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
- Adjacent
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:A/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.
-
Verify NX-OS versionRun 'show version' on the switch CLI to display the installed NX-OS software versionAffected if The displayed version shows exactly 5.2(5)
-
Confirm Nexus 7000 series modelRun 'show version' or 'show module' to identify the hardware platform. Look for Nexus 7000, 7009, 7010, 7018, or 7700 in the outputAffected if The device is a Nexus 7000 series switch
-
Check LLDP protocol statusRun 'show lldp status' to determine if LLDP is globally enabled on the deviceAffected if LLDP is globally enabled (output shows 'LLDP is enabled')
-
Verify LLDP is running on interfacesRun 'show lldp interface' to see which interfaces have LLDP transmission/reception enabledAffected if At least one interface has LLDP enabled for transmit or receive
Your environment is affected if you are running exactly NX-OS version 5.2(5) on a Nexus 7000 series switch with LLDP enabled on any interface, as the malformed LLDP packet DoS can only trigger when LLDP is active.
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 dataApply the Cisco patch for NX-OS 5.2(5) addressing Bug ID CSCud89415. If patching is not immediately feasible, consider disabling LLDP on untrusted interfaces or implementing network access controls to limit LLDP packet exposure to trusted segments.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-4197 — 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-4197 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