iOSOperating system · Cisco
CVE-2014-3273
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 LLDP implementation in Cisco IOS allows remote attackers to cause a denial of service (device reload) via a malformed packet, aka Bug ID CSCum96282.
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 confidenceThe LLDP (Link Layer Discovery Protocol) implementation in Cisco IOS contains a vulnerability where processing malformed LLDP packets triggers a denial of service condition causing the device to reload. This is a remote, network-based attack requiring no authentication.
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
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
- 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 if LLDP is enabled on the deviceRun the command 'show lldp' or 'show lldp status' in Cisco IOS privileged exec mode. Look for 'LLDP is enabled' in the output.Affected if LLDP is globally enabled (the device processes LLDP packets and is vulnerable to malformed packet attacks)
-
Identify interfaces with LLDP runningRun 'show lldp interface' to list all interfaces where LLDP is enabled.Affected if Any interface has LLDP enabled, especially those connected to untrusted or external networks
-
Determine which LLDP-enabled interfaces face untrusted networksReview the interface list from the previous step and map each LLDP-enabled interface to its network segment. Check if any connect to external networks, ISP connections, or untrusted downstream networks.Affected if LLDP is enabled on interfaces connected to untrusted or external-facing network segments
-
Check the Cisco IOS versionRun 'show version' and note the IOS release number in the output.Affected if Any Cisco IOS version is installed (according to the advisory, all versions are affected)
The environment is affected if LLDP is enabled on the device, particularly on interfaces that accept packets from untrusted network sources, since the vulnerability is triggered by malformed LLDP packets received on any enabled interface.
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 dataDisable LLDP on untrusted or external-facing interfaces, or implement network segmentation/firewall rules to block LLDP packets from untrusted sources.
Fix this in iOS
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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 $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-3273 — 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-3273 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