CVE-2018-0167
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 · uneditedMultiple Buffer Overflow vulnerabilities in the Link Layer Discovery Protocol (LLDP) subsystem of Cisco IOS Software, Cisco IOS XE Software, and Cisco IOS XR Software could allow an unauthenticated, adjacent attacker to cause a denial of service (DoS) condition or execute arbitrary code with elevated privileges on an affected device. Cisco Bug IDs: CSCuo17183, CSCvd73487.
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 confidenceMultiple buffer overflow vulnerabilities exist in Cisco's Link Layer Discovery Protocol (LLDP) implementation across IOS, IOS XE, and IOS XR software. An unauthenticated attacker on the adjacent network can send specially crafted LLDP packets to cause denial of service or execute arbitrary code with elevated privileges on affected 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.0.base<= 15.6.3m1<= 15.2\(6\)e0a<= 15.2\(4a\)ea5= 5.2.0.base<= 15.6.3m1<= 15.2\(6\)e0a<= 15.2\(4a\)ea5>= 4.1, < 5.1.3CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/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.
-
Identify the Cisco software productRun 'show version' to determine if the device runs iOS, iOS XE, or iOS XRAffected if Product is Cisco iOS, iOS XE, or iOS XR and version falls within affected ranges
-
Check the iOS/iOS XE version numberRun 'show version' and locate the version string (e.g., 15.2(4a)ea5, 15.6(3)m1, 15.2(6)e0a)Affected if Version equals 5.2.0.base, is less than or equal to 15.6.3m1, is less than or equal to 15.2(6)e0a, or is less than or equal to 15.2(4a)ea5
-
Check the IOS XR version numberRun 'show version' for IOS XR devices and locate the version stringAffected if Version is greater than or equal to 4.1 and less than 5.1.3
-
Verify if LLDP is enabledRun 'show lldp' or 'show lldp neighbors' to check LLDP status; run 'show run | include lldp' to check configurationAffected if LLDP is globally enabled or enabled on any interface (vulnerability only applies when LLDP is active)
-
Check for LLDP-enabled interfacesRun 'show lldp interface' to list interfaces with LLDP transmit or receive enabledAffected if Any interface has LLDP transmit or receive capability enabled
Device is affected if it runs a vulnerable iOS/iOS XE/IOS XR version AND has LLDP globally enabled or enabled on at least one 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.
dbcve · scoped5.1.3
Apply Cisco security patches for CSCuo17183 and CSCvd73487. Until patches are applied, consider disabling LLDP on untrusted network segments to reduce the attack surface.
Cisco IOS XR fixed in 5.1.3 and later; Cisco IOS/IOS XE fixed in later 15.x releases per cisco-sa-20180502-lldp advisory
- 1. Identify the exact Cisco IOS, IOS XE, or IOS XR version running on the device using the 'show version' command
- 2. Determine the product platform and model to ensure compatibility with the fixed release
- 3. Review Cisco Security Advisory cisco-sa-20180502-lldp for the complete list of fixed releases for your specific platform
- 4. Download the appropriate fixed Cisco IOS/IOS XE/IOS XR software image from Cisco.com or your Cisco smart account
- 5. Plan a maintenance window as upgrade requires device reload
- 6. Backup current device configuration using 'copy running-config startup-config' or archive the configuration
- 7. Transfer the new software image to the device using TFTP, FTP, SCP, or USB
- 8. Set the boot system to point to the new image using 'boot system <image>' in global configuration mode
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0167 — 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-2018-0167 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