CVE-2017-16930

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

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, 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: 34%CVSS: 9.8Exploit: NoneExposed: 0

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

The remote management interface on the Claymore Dual GPU miner 10.1 allows an unauthenticated remote attacker to execute arbitrary code due to a stack-based buffer overflow in the request handler. This can be exploited via a long API request that is mishandled during logging.

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

Published

December 5, 2017

Last Modified

May 13, 2026

Advisory Details (3)

Auto-updated May 17, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

Claymore Dual ETH + DCR/SC/LBC/PASC GPU Miner - Stack Buffer Overflow / Path Traversal - Windows remote Exploit

https://www.exploit-db.com/exploits/43231/
generic🟡 PoC Available

pub/pocs/cve-2017-16930 at master · tintinweb/pub · GitHub

https://github.com/tintinweb/pub/tree/master/pocs/cve-2017-16930
generic🟡 PoC Available

oss-security - CVE-2017-16930 - Claymore's Dual Ethereum Miner unauth stack buffer overflow in remote management interface

http://www.openwall.com/lists/oss-security/2017/12/04/3

Data Freshness Timeline

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

Publicly available exploits

(1 reference)

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

  • Exploit-DBEDB-43231
    First seen Dec 7, 2017

    Claymore Dual ETH + DCR/SC/LBC/PASC GPU Miner - Stack Buffer Overflow / Path Traversal

    Open source ↗

Frequently asked(5)

What is CVE-2017-16930?
CVE-2017-16930 is a critical vulnerability published on December 5, 2017. The remote management interface on the Claymore Dual GPU miner 10.1 allows an unauthenticated remote attacker to execute arbitrary code due to a stack-based buffer overflow in the request handler. This can be exploited via a long API request that is mishandled during logging.
When was CVE-2017-16930 disclosed?
CVE-2017-16930 was first published in the National Vulnerability Database on December 5, 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-16930 actively exploited?
CVE-2017-16930 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-16930?
CVE-2017-16930 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2017-16930?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-16930, 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-16930

Explore →

Is Your Infrastructure Affected by CVE-2017-16930?

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

Start Free Scan →Browse All CVEs