iOSOperating system · Cisco
CVE-2016-1424
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 IOS 15.2(1)T1.11 and 15.2(2)TST allows remote attackers to cause a denial of service (device crash) via a crafted LLDP packet, aka Bug ID CSCun63132.
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 IOS where malformed Link Layer Discovery Protocol (LLDP) packets cause affected devices to crash. Attackers send specially crafted LLDP packets to trigger the crash without authentication, requiring only network adjacency to the targeted device.
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
iOSOperating system
= 15.2\(1\)t1.11= 15.2\(2\)tstCVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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 LLDP is enabled on the deviceRun the command 'show lldp' or 'show lldp neighbors' in privileged exec mode. If LLDP is disabled, the device will respond with '%LLDP is not enabled' or similar message.Affected if LLDP is globally enabled or enabled on any interface (the vulnerability requires LLDP to be running to receive the malformed packets)
-
Identify interfaces with LLDP enabledRun 'show lldp interface' to list all interfaces where LLDP is actively transmitting and receiving.Affected if Any interface has LLDP enabled (Tx and Rx), meaning it can receive the malicious LLDP packets
-
Determine the installed Cisco IOS versionRun 'show version' and locate the 'IOS' version string (typically displayed as something like 15.2(1)T1 or 15.2(2)T) in the output.Affected if The version exactly matches 15.2(1)t1.11 or 15.2(2)tst (these are the specific affected versions)
-
Confirm the full IOS release train and rebuildIn 'show version' output, examine the full version number including the rebuild suffix (e.g., t1.11) to confirm if it matches the exact affected versions.Affected if The complete version string matches one of the two specific affected versions listed
The device is affected if LLDP is enabled AND the Cisco IOS version exactly matches 15.2(1)t1.11 or 15.2(2)tst.
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 IOS security update for Bug ID CSCun63132, or disable LLDP on vulnerable interfaces as a temporary workaround if patching is not immediately feasible.
Fix this in iOS
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.0 h
- Testing2.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,488.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-1424 — 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-2016-1424 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