CVE-2017-6079

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 47%CVSS: 9.8Exploit: NoneExposed: 0

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

The HTTP web-management application on Edgewater Networks Edgemarc appliances has a hidden page that allows for user-defined commands such as specific iptables routes, etc., to be set. You can use this page as a web shell essentially to execute commands, though you get no feedback client-side from the web application: if the command is valid, it executes. An example is the wget command. The page that allows this has been confirmed in firmware as old as 2006.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
98.7%
KEV
Not listed

Published

May 16, 2017

Last Modified

May 13, 2026

Advisory Details (1)

Auto-updated May 14, 2026
No patch confirmed yet.
generic

CVE-2017-6079 – Blind Command Injection In Edgewater Edgemarc Devices | Depth Security

https://depthsecurity.com/blog/cve-2017-6079-blind-command-injection-in-edgewater-edgemarc-devices

Data Freshness Timeline

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

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCMostafaSoliman/CVE-2017-6079-Blind-Command-Injection-In-Edgewater-Edgemarc-Devices-Exploit
    First seen Sep 22, 2018
    Open source ↗

Frequently asked(5)

What is CVE-2017-6079?
CVE-2017-6079 is a critical vulnerability published on May 16, 2017. The HTTP web-management application on Edgewater Networks Edgemarc appliances has a hidden page that allows for user-defined commands such as specific iptables routes, etc., to be set. You can use this page as a web shell essentially to execute commands, though you get no feedback client-side from…
When was CVE-2017-6079 disclosed?
CVE-2017-6079 was first published in the National Vulnerability Database on May 16, 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-6079 actively exploited?
CVE-2017-6079 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-6079?
CVE-2017-6079 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2017-6079?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-6079, 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-6079

Explore →

Is Your Infrastructure Affected by CVE-2017-6079?

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