CVE-2018-0395 json
Cisco FXOS and NX-OS Software Link Layer Discovery Protocol Denial of Service Vulnerability
published 2018-10-17 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-1218
- cvss
- 8.8
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 56%
- public exploits
- 0
- none known
Summary
A vulnerability in the Link Layer Discovery Protocol (LLDP) implementation for Cisco FXOS Software and Cisco NX-OS Software could allow an unauthenticated, adjacent attacker to cause a denial of service (DoS) condition when the device unexpectedly reloads. The vulnerability is due to improper input validation of certain type, length, value (TLV) fields of the LLDP frame header. An attacker could exploit this vulnerability by sending a crafted LLDP packet to an interface on the targeted device. A successful exploit could allow the attacker to cause the switch to reload unexpectedly.
Patch / fix
- Cisco Cisco NX-OS Software 6.2(1)
- Cisco Firepower 4100 Series Next-Generation Firewalls <2.3.1.58
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 23 mo ago
Exploit prediction
0.79% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 8.8 | CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.0 | 5.3 | CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 2.9 | AV:A/AC:M/Au:N/C:N/I:N/A:P |
Affected products
- Cisco Cisco NX-OS Software
- Cisco Firepower 4100 Series Next-Generation Firewalls
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
tools.cisco.com
/security/center/content/CiscoSecurityAdvisory/cisco-sa-20181017-fxnx-os-dos
vendor-advisory
-
securitytracker.com
/id/1041919
vdb-entry, third-party-advisory
-
securityfocus.com
/bid/105674
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2018-0395
- NVD CVE-2018-0395
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.