FKIE_CVE-2026-20010
Vulnerability from fkie_nvd - Published: 2026-02-25 17:25 - Updated: 2026-04-15 00:35
Severity ?
Summary
A vulnerability in the Link Layer Discovery Protocol (LLDP) feature of Cisco NX-OS Software could allow an unauthenticated, adjacent attacker to cause the LLDP process to restart, which could cause an affected device to reload unexpectedly.
This vulnerability is due to improper handling of specific fields in an LLDP frame. An attacker could exploit this vulnerability by sending a crafted LLDP packet to an interface of an affected device. A successful exploit could allow the attacker to cause the device to reload, resulting in a denial of service (DoS) condition.
Note: LLDP is a Layer 2 link protocol. To exploit this vulnerability, an attacker would need to be directly connected to an interface of an affected device, either physically or logically (for example, through a Layer 2 Tunnel configured to transport the LLDP protocol).
References
Impacted products
| Vendor | Product | Version |
|---|
{
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "A vulnerability in the Link Layer Discovery Protocol (LLDP) feature of Cisco NX-OS Software could allow an unauthenticated, adjacent attacker to cause the LLDP process to restart, which could cause an affected device to reload unexpectedly.\r\n\r\nThis vulnerability is due to improper handling of specific fields in an LLDP frame. An attacker could exploit this vulnerability by sending a crafted LLDP packet to an interface of an affected device. A successful exploit could allow the attacker to cause the device to reload, resulting in a denial of service (DoS) condition.\r\nNote:\u0026nbsp;LLDP is a Layer 2 link protocol. To exploit this vulnerability, an attacker would need to be\u0026nbsp;directly connected to an interface of an affected device, either physically or logically (for example, through a Layer 2 Tunnel configured to transport the LLDP protocol)."
},
{
"lang": "es",
"value": "Una vulnerabilidad en la funci\u00f3n del Protocolo de Descubrimiento de Capa de Enlace (LLDP) del software Cisco NX-OS podr\u00eda permitir a un atacante adyacente no autenticado provocar el reinicio del proceso LLDP, lo que podr\u00eda causar que un dispositivo afectado se recargue inesperadamente.\n\nEsta vulnerabilidad se debe al manejo inadecuado de campos espec\u00edficos en una trama LLDP. Un atacante podr\u00eda explotar esta vulnerabilidad enviando un paquete LLDP manipulado a una interfaz de un dispositivo afectado. Un exploit exitoso podr\u00eda permitir al atacante provocar la recarga del dispositivo, lo que resultar\u00eda en una condici\u00f3n de denegaci\u00f3n de servicio (DoS).\nNota: LLDP es un protocolo de enlace de Capa 2. Para explotar esta vulnerabilidad, un atacante necesitar\u00eda estar directamente conectado a una interfaz de un dispositivo afectado, ya sea f\u00edsica o l\u00f3gicamente (por ejemplo, a trav\u00e9s de un t\u00fanel de Capa 2 configurado para transportar el protocolo LLDP)."
}
],
"id": "CVE-2026-20010",
"lastModified": "2026-04-15T00:35:42.020",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "ADJACENT_NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.4,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "CHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.8,
"impactScore": 4.0,
"source": "psirt@cisco.com",
"type": "Primary"
}
]
},
"published": "2026-02-25T17:25:24.110",
"references": [
{
"source": "psirt@cisco.com",
"url": "https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-n3kn9k_aci_lldp_dos-NdgRrrA3"
}
],
"sourceIdentifier": "psirt@cisco.com",
"vulnStatus": "Deferred",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-805"
}
],
"source": "psirt@cisco.com",
"type": "Primary"
}
]
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…