CVE-2017-7649

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-17. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
9.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.6%CVSS: 9.8Exploit: None knownExposed services: Not assessed

No fix has been recorded since the CVE record was published in 2017 — if the vendor still supports the product, apply the fixed version it names; if not, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

The network enabled distribution of Kura before 2.1.0 takes control over the device's firewall setup but does not allow IPv6 firewall rules to be configured. Still the Equinox console port 5002 is left open, allowing to log into Kura without any user credentials over unencrypted telnet and executing commands using the Equinox "exec" command. As the process is running as "root" full control over the device can be acquired. IPv6 is also left in auto-configuration mode, accepting router advertisements automatically and assigns a MAC address based IPv6 address.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
49
EG Risk 49/100

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 (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation1.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability30% × 15%
EchelonGraph's default before algorithm v3.4: CISA had not published Automatable for this CVE.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact total (CVSS ≥ 9.0). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix has been recorded since the CVE record was published in 2017. If the vendor still supports the product, apply the fixed version it names within your standard update timelines at low or medium mission impact and sooner than that at high; if it no longer does, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.
EPSS PROB
1.6%
EPSS %ILE
75th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).

No fix has been recorded since the CVE record was published in 2017. If the vendor still supports the product, apply the fixed version it names within your standard update timelines at low or medium mission impact and sooner than that at high; if it no longer does, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact total (CVSS ≥ 9.0). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

Published

September 11, 2017

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Oct 5, 2026
No fix on record since 2017.
Web page

[Sec] Kura firewall rules bypassed with IPv6 · Issue #956 · eclipse-kura/kura · GitHub

https://github.com/eclipse/kura/issues/956
Web page

514681 – (CVE-2017-7649) CVE-2017-7649: Remote code execution vulnerability over IPv6

https://bugs.eclipse.org/bugs/show_bug.cgi?id=514681

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 26× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 83 of 183 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 17 repeat rows among the latest 100 are merged into the row they repeat. The 100 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-11 13:41 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  2. 2026-10-10 19:55 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  3. 2026-10-09 20:02 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  4. 2026-10-08 16:36 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  5. 2026-10-07 23:41 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  6. 2026-10-06 15:12 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  7. 2026-10-05 17:39 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  8. 2026-10-04 23:18 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  9. 2026-10-04 06:04 UTCOSV refresh
  10. 2026-10-03 14:21 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  11. 2026-09-30 14:59 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  12. 2026-09-30 09:40 UTCEG score recompute
  13. 2026-09-28 13:45 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  14. 2026-09-27 13:40 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  15. 2026-09-26 15:53 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  16. 2026-09-26 00:19 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  17. 2026-09-24 13:59 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  18. 2026-09-23 13:42 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  19. 2026-09-21 20:27 UTCEPSS rescoreEPSS 1.5% · 72nd percentile
  20. 2026-09-20 20:09 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  21. 2026-09-19 15:36 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  22. 2026-09-17 19:22 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  23. 2026-09-15 03:05 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  24. 2026-09-14 20:14 UTCOSV refresh
  25. 2026-09-13 16:42 UTCEPSS rescoreEPSS 1.6% · 75th percentile
Show 58 more
  1. 2026-09-12 14:56 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  2. 2026-09-11 09:31 UTCEPSS rescoreEPSS 1.6% · 75th percentile
  3. 2026-09-07 15:56 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  4. 2026-09-05 15:24 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  5. 2026-09-04 13:56 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  6. 2026-09-04 05:02 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  7. 2026-09-02 14:07 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  8. 2026-09-01 03:31 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  9. 2026-08-30 19:13 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  10. 2026-08-28 21:36 UTCEPSS rescoreEPSS 1.5% · 71st percentile
  11. 2026-08-27 14:21 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  12. 2026-08-26 19:46 UTCOSV refresh
  13. 2026-08-26 14:41 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  14. 2026-08-25 13:44 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  15. 2026-08-23 00:14 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  16. 2026-08-21 23:44 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  17. 2026-08-19 16:59 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  18. 2026-08-18 13:43 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  19. 2026-08-16 14:51 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  20. 2026-08-16 02:10 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  21. 2026-08-15 01:26 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  22. 2026-08-12 13:46 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  23. 2026-08-10 10:09 UTCOSV refresh
  24. 2026-08-09 13:42 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  25. 2026-08-08 16:32 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  26. 2026-08-07 16:22 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  27. 2026-08-06 13:42 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  28. 2026-08-05 19:13 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  29. 2026-08-02 02:23 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  30. 2026-08-01 04:12 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  31. 2026-07-30 16:24 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  32. 2026-07-30 01:26 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  33. 2026-07-28 15:32 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  34. 2026-07-26 14:51 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  35. 2026-07-25 10:41 UTCOSV refresh
  36. 2026-07-23 14:15 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  37. 2026-07-23 01:30 UTCEG score recompute
  38. 2026-07-22 22:10 UTCEG score recompute
  39. 2026-07-22 14:04 UTCEPSS rescoreEPSS 1.6% · 74th percentile
  40. 2026-07-21 15:21 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  41. 2026-07-20 17:04 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  42. 2026-07-19 14:28 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  43. 2026-07-19 02:26 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  44. 2026-07-18 10:01 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  45. 2026-07-16 16:59 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  46. 2026-07-15 16:54 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  47. 2026-07-15 01:56 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  48. 2026-07-13 22:26 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  49. 2026-07-12 05:43 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  50. 2026-07-11 08:24 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  51. 2026-07-09 19:06 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  52. 2026-07-08 15:11 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  53. 2026-07-08 05:05 UTCOSV refresh
  54. 2026-07-07 13:42 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  55. 2026-07-06 16:24 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  56. 2026-07-06 02:20 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  57. 2026-07-05 02:27 UTCEPSS rescoreEPSS 1.6% · 73rd percentile
  58. 2026-07-04 06:28 UTCEPSS rescoreEPSS 1.6% · 73rd percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2017-7649?
CVE-2017-7649 is a critical-severity vulnerability; its CVE record was published on September 11, 2017. The network enabled distribution of Kura before 2.1.0 takes control over the device's firewall setup but does not allow IPv6 firewall rules to be configured. Still the Equinox console port 5002 is left open, allowing to log into Kura without any user credentials over unencrypted telnet and…
When was CVE-2017-7649 made public?
CVE-2017-7649 was made public on April 4, 2017: that is the date its CVE record's CNA, Eclipse Foundation, gives for when the vulnerability was made public. The CVE record itself was published on September 11, 2017. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2017-7649 actively exploited?
CVE-2017-7649 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.6% probability of exploitation in the next 30 days (75th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2017-7649?
CVE-2017-7649 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2017-7649?
No fix for CVE-2017-7649 has been recorded since its CVE record was published in 2017. If the vendor still supports the product, apply the fixed version it names; if it no longer does, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2017-7649?

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

Book a Demo →Browse All CVEs