CVE-2017-12238

CRITICALNVD 6.59.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-03-03), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 6.5 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, ghsa, nvd
Trending — 3 sources updated this weekExploited in the wild
9.0EG
EchelonGraph verdictMitigate nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 2.0%CVSS: 6.5Exploit: cisa kev · ssvc activeExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

A vulnerability in the Virtual Private LAN Service (VPLS) code of Cisco IOS 15.0 through 15.4 for Cisco Catalyst 6800 Series Switches could allow an unauthenticated, adjacent attacker to cause a C6800-16P10G or C6800-16P10G-XL type line card to crash, resulting in a denial of service (DoS) condition. The vulnerability is due to a memory management issue in the affected software. An attacker could exploit this vulnerability by creating a large number of VPLS-generated MAC entries in the MAC address table of an affected device. A successful exploit could allow the attacker to cause a C6800-16P10G or C6800-16P10G-XL type line card to crash, resulting in a DoS condition. This vulnerability affects Cisco Catalyst 6800 Series Switches that are running a vulnerable release of Cisco IOS Software and have a Cisco C6800-16P10G or C6800-16P10G-XL line card in use with Supervisor Engine 6T. To be vulnerable, the device must also be configured with VPLS and the C6800-16P10G or C6800-16P10G-XL line card needs to be the core-facing MPLS interfaces. Cisco Bug IDs: CSCva61927.

CVSS v3
6.5
EG Score
9.0CRITICALhigh confidence
EG Risk
81
EG Risk 81/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation100% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
2.0%
EPSS %ILE
80th
KEV
⚠ Exploited

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 29, 2017

Last Modified

June 17, 2026

Advisory Details (4)

Auto-updated May 20, 2026
⚠️ Active exploitation confirmed. No fix on record yet. Sources: cisa.
cisa🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2017-12238
generic

Cisco IOS Software for Cisco Catalyst 6800 Series Switches VPLS Denial of Service Vulnerability

https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20170927-vpls

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 59× in last 7d / 256× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 1,138 total refreshes for this CVE.

  1. 2026-10-10 05:44 UTCGHSA enrichment
  2. 2026-10-10 02:02 UTCGHSA enrichment
  3. 2026-10-09 22:19 UTCEG score recompute
  4. 2026-10-09 22:19 UTCGHSA enrichment
  5. 2026-10-09 20:02 UTCEPSS rescore
  6. 2026-10-09 18:34 UTCGHSA enrichment
  7. 2026-10-09 14:51 UTCGHSA enrichment
  8. 2026-10-09 11:05 UTCGHSA enrichment
  9. 2026-10-09 07:21 UTCGHSA enrichment
  10. 2026-10-09 03:38 UTCGHSA enrichment
  11. 2026-10-08 23:55 UTCGHSA enrichment
  12. 2026-10-08 20:12 UTCEG score recompute
  13. 2026-10-08 20:12 UTCGHSA enrichment
  14. 2026-10-08 16:35 UTCEPSS rescore
  15. 2026-10-08 16:30 UTCGHSA enrichment
  16. 2026-10-08 12:44 UTCGHSA enrichment
  17. 2026-10-08 08:58 UTCGHSA enrichment
  18. 2026-10-08 05:16 UTCGHSA enrichment
  19. 2026-10-08 01:33 UTCEG score recompute
  20. 2026-10-08 01:33 UTCGHSA enrichment
  21. 2026-10-07 23:41 UTCEPSS rescore
  22. 2026-10-07 21:50 UTCGHSA enrichment
  23. 2026-10-07 18:07 UTCGHSA enrichment
  24. 2026-10-07 14:24 UTCGHSA enrichment
  25. 2026-10-07 10:41 UTCGHSA enrichment
Show 75 more
  1. 2026-10-07 06:58 UTCGHSA enrichment
  2. 2026-10-07 03:15 UTCGHSA enrichment
  3. 2026-10-06 23:32 UTCGHSA enrichment
  4. 2026-10-06 19:49 UTCGHSA enrichment
  5. 2026-10-06 16:07 UTCEG score recompute
  6. 2026-10-06 16:07 UTCGHSA enrichment
  7. 2026-10-06 15:11 UTCEPSS rescore
  8. 2026-10-06 12:24 UTCGHSA enrichment
  9. 2026-10-06 08:41 UTCGHSA enrichment
  10. 2026-10-06 04:57 UTCGHSA enrichment
  11. 2026-10-06 01:14 UTCGHSA enrichment
  12. 2026-10-05 21:28 UTCGHSA enrichment
  13. 2026-10-05 17:43 UTCEG score recompute
  14. 2026-10-05 17:43 UTCGHSA enrichment
  15. 2026-10-05 17:38 UTCEPSS rescore
  16. 2026-10-05 14:00 UTCGHSA enrichment
  17. 2026-10-05 10:17 UTCGHSA enrichment
  18. 2026-10-05 06:34 UTCGHSA enrichment
  19. 2026-10-05 02:51 UTCEG score recompute
  20. 2026-10-05 02:51 UTCGHSA enrichment
  21. 2026-10-04 23:18 UTCEPSS rescore
  22. 2026-10-04 23:05 UTCGHSA enrichment
  23. 2026-10-04 19:21 UTCGHSA enrichment
  24. 2026-10-04 15:39 UTCGHSA enrichment
  25. 2026-10-04 11:56 UTCGHSA enrichment
  26. 2026-10-04 08:13 UTCGHSA enrichment
  27. 2026-10-04 04:31 UTCGHSA enrichment
  28. 2026-10-04 00:48 UTCGHSA enrichment
  29. 2026-10-03 21:06 UTCGHSA enrichment
  30. 2026-10-03 17:22 UTCEG score recompute
  31. 2026-10-03 17:22 UTCGHSA enrichment
  32. 2026-10-03 14:21 UTCEPSS rescore
  33. 2026-10-03 13:40 UTCGHSA enrichment
  34. 2026-10-03 09:57 UTCGHSA enrichment
  35. 2026-10-03 06:13 UTCGHSA enrichment
  36. 2026-10-03 02:30 UTCGHSA enrichment
  37. 2026-10-02 22:47 UTCGHSA enrichment
  38. 2026-10-02 19:03 UTCEG score recompute
  39. 2026-10-02 19:03 UTCGHSA enrichment
  40. 2026-10-02 15:18 UTCGHSA enrichment
  41. 2026-10-02 11:34 UTCGHSA enrichment
  42. 2026-10-02 07:48 UTCGHSA enrichment
  43. 2026-10-02 04:06 UTCGHSA enrichment
  44. 2026-10-02 00:21 UTCGHSA enrichment
  45. 2026-10-01 20:39 UTCEG score recompute
  46. 2026-10-01 20:39 UTCGHSA enrichment
  47. 2026-10-01 16:56 UTCGHSA enrichment
  48. 2026-10-01 13:10 UTCGHSA enrichment
  49. 2026-10-01 09:28 UTCGHSA enrichment
  50. 2026-10-01 05:45 UTCGHSA enrichment
  51. 2026-10-01 02:03 UTCGHSA enrichment
  52. 2026-09-30 22:19 UTCGHSA enrichment
  53. 2026-09-30 18:36 UTCEG score recompute
  54. 2026-09-30 18:36 UTCGHSA enrichment
  55. 2026-09-30 14:58 UTCEPSS rescore
  56. 2026-09-30 14:51 UTCGHSA enrichment
  57. 2026-09-30 11:09 UTCGHSA enrichment
  58. 2026-09-30 07:26 UTCGHSA enrichment
  59. 2026-09-30 03:43 UTCGHSA enrichment
  60. 2026-09-30 00:00 UTCGHSA enrichment
  61. 2026-09-29 20:16 UTCGHSA enrichment
  62. 2026-09-29 16:32 UTCEG score recompute
  63. 2026-09-29 16:32 UTCGHSA enrichment
  64. 2026-09-29 12:48 UTCGHSA enrichment
  65. 2026-09-29 09:05 UTCGHSA enrichment
  66. 2026-09-29 05:20 UTCGHSA enrichment
  67. 2026-09-29 01:38 UTCGHSA enrichment
  68. 2026-09-28 21:55 UTCEG score recompute
  69. 2026-09-28 21:55 UTCGHSA enrichment
  70. 2026-09-28 18:13 UTCGHSA enrichment
  71. 2026-09-28 14:28 UTCEG score recompute
  72. 2026-09-28 14:28 UTCGHSA enrichment
  73. 2026-09-28 13:45 UTCEPSS rescore
  74. 2026-09-28 10:45 UTCGHSA enrichment
  75. 2026-09-28 07:02 UTCGHSA enrichment

Frequently asked(6)

What is CVE-2017-12238?
CVE-2017-12238 is a critical vulnerability published on September 29, 2017. A vulnerability in the Virtual Private LAN Service (VPLS) code of Cisco IOS 15.0 through 15.4 for Cisco Catalyst 6800 Series Switches could allow an unauthenticated, adjacent attacker to cause a C6800-16P10G or C6800-16P10G-XL type line card to crash, resulting in a denial of service (DoS)…
When was CVE-2017-12238 disclosed?
CVE-2017-12238 was first published on September 29, 2017, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-12238 actively exploited?
Yes. CISA added CVE-2017-12238 to the Known Exploited Vulnerabilities catalog on March 3, 2022, affecting Cisco Catalyst 6800 Series Switches. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation, and watch the vendor's advisory for the fix.
What is the CVSS score of CVE-2017-12238?
CVE-2017-12238 has a CVSS v3 base score of 6.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
Which products are affected by CVE-2017-12238?
CVE-2017-12238 affects Cisco Catalyst 6800 Series Switches.
How do I remediate CVE-2017-12238?
No fix for CVE-2017-12238 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2017-12238

Explore →

Is Your Infrastructure Affected by CVE-2017-12238?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.