CVE-2017-1000375

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
Weaponized
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 19%CVSS: 9.8Exploit: NoneExposed: 0

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

NetBSD maps the run-time link-editor ld.so directly below the stack region, even if ASLR is enabled, this allows attackers to more easily manipulate memory leading to arbitrary code execution. This affects NetBSD 7.1 and possibly earlier versions.

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

Published

June 19, 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
https://www.qualys.com/2017/06/19/stack-clash/stack-clash.txt
generic🟡 PoC Available

NetBSD - 'Stack Clash' (PoC) - NetBSD_x86 dos Exploit

https://www.exploit-db.com/exploits/42272/
generic
http://www.securityfocus.com/bid/99257

Data Freshness Timeline

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

    NetBSD - 'Stack Clash' (PoC)

    Open source ↗

Frequently asked(5)

What is CVE-2017-1000375?
CVE-2017-1000375 is a critical vulnerability published on June 19, 2017. NetBSD maps the run-time link-editor ld.so directly below the stack region, even if ASLR is enabled, this allows attackers to more easily manipulate memory leading to arbitrary code execution. This affects NetBSD 7.1 and possibly earlier versions.
When was CVE-2017-1000375 disclosed?
CVE-2017-1000375 was first published in the National Vulnerability Database on June 19, 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-1000375 actively exploited?
CVE-2017-1000375 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 97.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-1000375?
CVE-2017-1000375 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2017-1000375?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-1000375, 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-1000375

Explore →

Is Your Infrastructure Affected by CVE-2017-1000375?

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

Start Free Scan →Browse All CVEs