CVE-2017-12336

MEDIUMNVD 4.24.2—
EchelonGraph scoreMEDIUM confidence

Score 4.2 from GitHub Security Advisory published 2022-05-17. NVD baseline CVSS 4.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
4.2
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.2Exploit: NoneExposed: 0

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

A vulnerability in the TCL scripting subsystem of Cisco NX-OS System Software could allow an authenticated, local attacker to escape the interactive TCL shell and gain unauthorized access to the underlying operating system of the device. The vulnerability exists due to insufficient input validation of user-supplied files passed to the interactive TCL shell of the affected device. An attacker could exploit this vulnerability to escape the scripting sandbox and execute arbitrary commands on the underlying operating system with the privileges of the authenticated user. To exploit this vulnerability, an attacker must have local access and be authenticated to the targeted device with administrative or tclsh execution privileges. This vulnerability affects the following products running Cisco NX-OS System Software: Multilayer Director Switches, Nexus 2000 Series Fabric Extenders, Nexus 3000 Series Switches, Nexus 3500 Platform Switches, Nexus 5000 Series Switches, Nexus 5500 Platform Switches, Nexus 5600 Platform Switches, Nexus 6000 Series Switches, Nexus 7000 Series Switches, Nexus 7700 Series Switches, Nexus 9000 Series Switches in standalone NX-OS mode, Nexus 9500 R-Series Line Cards and Fabric Modules, Unified Computing System Manager. Cisco Bug IDs: CSCve93750, CSCve93762, CSCve93763, CSCvg04127.

CVSS v3
4.2
EG Score
4.2(medium)
EPSS
34.4%
KEV
Not listed

Published

November 30, 2017

Last Modified

May 13, 2026

References (6)

Data Freshness Timeline

(refreshed 9× in last 7d / 37× 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.

  1. 2026-07-07 13:42 UTCEPSS rescore
  2. 2026-07-06 16:24 UTCEPSS rescore
  3. 2026-07-06 02:20 UTCEPSS rescore
  4. 2026-07-05 02:27 UTCEPSS rescore
  5. 2026-07-04 06:28 UTCEPSS rescore
  6. 2026-07-01 15:02 UTCEPSS rescore
  7. 2026-07-01 15:02 UTCEPSS rescore
  8. 2026-06-30 23:19 UTCEPSS rescore
  9. 2026-06-30 23:19 UTCEPSS rescore
  10. 2026-06-28 14:04 UTCEPSS rescore
  11. 2026-06-28 04:53 UTCEPSS rescore
  12. 2026-06-27 03:05 UTCEPSS rescore
  13. 2026-06-25 13:47 UTCEPSS rescore
  14. 2026-06-25 13:47 UTCEPSS rescore
  15. 2026-06-24 14:02 UTCEPSS rescore
  16. 2026-06-23 21:30 UTCEPSS rescore
  17. 2026-06-22 14:23 UTCEPSS rescore
  18. 2026-06-22 14:23 UTCEPSS rescore
  19. 2026-06-21 14:54 UTCEPSS rescore
  20. 2026-06-21 14:54 UTCEPSS rescore
  21. 2026-06-21 01:57 UTCEPSS rescore
  22. 2026-06-21 01:57 UTCEPSS rescore
  23. 2026-06-19 19:23 UTCEPSS rescore
  24. 2026-06-19 19:23 UTCEPSS rescore
  25. 2026-06-18 17:50 UTCEPSS rescore
Show 45 more
  1. 2026-06-17 17:50 UTCEPSS rescore
  2. 2026-06-16 17:50 UTCEPSS rescore
  3. 2026-06-15 17:45 UTCEPSS rescore
  4. 2026-06-14 23:14 UTCEPSS rescore
  5. 2026-06-14 23:14 UTCEPSS rescore
  6. 2026-06-13 22:57 UTCEPSS rescore
  7. 2026-06-12 23:09 UTCEPSS rescore
  8. 2026-06-11 13:57 UTCEPSS rescore
  9. 2026-06-10 22:15 UTCEPSS rescore
  10. 2026-06-08 14:14 UTCEPSS rescore
  11. 2026-06-07 15:22 UTCEPSS rescore
  12. 2026-06-07 15:22 UTCEPSS rescore
  13. 2026-06-06 13:45 UTCEPSS rescore
  14. 2026-06-06 13:45 UTCEPSS rescore
  15. 2026-06-05 22:44 UTCEPSS rescore
  16. 2026-06-05 06:08 UTCEPSS rescore
  17. 2026-06-05 06:08 UTCEPSS rescore
  18. 2026-06-04 13:10 UTCEPSS rescore
  19. 2026-06-04 13:10 UTCEPSS rescore
  20. 2026-06-02 20:11 UTCEPSS rescore
  21. 2026-06-02 20:11 UTCEPSS rescore
  22. 2026-06-01 13:49 UTCEPSS rescore
  23. 2026-06-01 13:49 UTCEPSS rescore
  24. 2026-05-31 22:28 UTCEPSS rescore
  25. 2026-05-31 00:14 UTCEPSS rescore
  26. 2026-05-29 13:41 UTCEPSS rescore
  27. 2026-05-28 13:42 UTCEPSS rescore
  28. 2026-05-28 13:42 UTCEPSS rescore
  29. 2026-05-27 13:38 UTCEPSS rescore
  30. 2026-05-27 13:38 UTCEPSS rescore
  31. 2026-05-26 13:42 UTCEPSS rescore
  32. 2026-05-26 13:42 UTCEPSS rescore
  33. 2026-05-26 07:17 UTCEPSS rescore
  34. 2026-05-26 07:17 UTCEPSS rescore
  35. 2026-05-22 21:15 UTCEPSS rescore
  36. 2026-05-22 21:15 UTCEPSS rescore
  37. 2026-05-22 21:15 UTCEPSS rescore
  38. 2026-05-22 07:38 UTCEG score recompute
  39. 2026-05-22 07:37 UTCGHSA enrichment
  40. 2026-05-20 22:37 UTCEPSS rescore
  41. 2026-05-20 22:37 UTCEPSS rescore
  42. 2026-05-20 11:21 UTCEPSS rescore
  43. 2026-05-20 11:21 UTCEPSS rescore
  44. 2026-05-18 21:30 UTCEPSS rescore
  45. 2026-05-18 21:30 UTCEPSS rescore

Frequently asked(5)

What is CVE-2017-12336?
CVE-2017-12336 is a medium vulnerability published on November 30, 2017. A vulnerability in the TCL scripting subsystem of Cisco NX-OS System Software could allow an authenticated, local attacker to escape the interactive TCL shell and gain unauthorized access to the underlying operating system of the device. The vulnerability exists due to insufficient input validation…
When was CVE-2017-12336 disclosed?
CVE-2017-12336 was first published in the National Vulnerability Database on November 30, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-12336 actively exploited?
CVE-2017-12336 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 34.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-12336?
CVE-2017-12336 has a CVSS v3 base score of 4.2 (NVD).
How do I remediate CVE-2017-12336?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-12336, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2017-12336?

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

Start Free Scan →Browse All CVEs