CVE-2017-7938

CRITICALNVD 6.69.8
EchelonGraph scoreMEDIUM confidence

“▲” beside the score: it is higher than NVD's CVSS score.

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Weaponized

Also known asEUVD-2017-16909 (ENISA EUVD) · GHSA-494m-pv6g-vh73 (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • Public exploit code is available (Exploit-DB, marked verified by Exploit-DB)
CISA-KEV: Not listedEPSS PROB: 5.0%CVSS: 6.6Exploit: Exploit-DB (verified)Exposed services: Not assessed

A fix is available — apply it.

Stack-based buffer overflow in DMitry (Deepmagic Information Gathering Tool) version 1.3a (Unix) allows attackers to cause a denial of service (application crash) or possibly have unspecified other impact via a long argument. An example threat model is automated execution of DMitry with hostname strings found in local log files.

CVSS v3
6.6
EG Score
9.8CRITICALmedium confidence
EG Risk
70
EG Risk 70/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation65% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 2 (Weaponized): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
5.0%
EPSS %ILE
92nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
5.0% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (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

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 20, 2017

Last Modified

June 17, 2026

Advisory Details (5)

Auto-updated Oct 14, 2026
Patch available. Sources: github_pr.
Web page

Dmitry 1.3a - Local Buffer Overflow (PoC) - Linux dos Exploit

https://www.exploit-db.com/exploits/41898/
Web page

Packet Storm

https://packetstormsecurity.com/files/142210/Dmitry-1.3a-Local-Stack-Buffer-Overflow.html
Web pageMentions a patch (unverified)

[SECURITY] [DLA 3933-1] dmitry security update

https://lists.debian.org/debian-lts-announce/2024/10/msg00024.html
GitHub pull request

Fix format string and buffer overflow vulnerabilities

Fix merged in jaygreig86/dmitry PR #12 on 2024-05-28 — awaiting tagged release

https://github.com/jaygreig86/dmitry/pull/12
Web page

Dmitry(Deepmagic Information Gathering Tool) Local Stack Buffer Overflow - CXSecurity.com

https://cxsecurity.com/issue/WLB-2017040113

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntudmitry (1.3a-1ubuntu0.16.04.1~esm1) @ xenial2026-11-11ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
dmitry1.3a-1.1
  • every version up to 1.3a-1.1+deb11u1: fixed in 1.3a-1.1+deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
dmitry1.3a-1.2
  • every version up to 1.3a-1.2+deb12u1: fixed in 1.3a-1.2+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
dmitry—
  • every version up to 1.3a-5: fixed in 1.3a-5
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
dmitry—
  • every version up to 1.3a-5: fixed in 1.3a-5
—

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 16× in last 7d / 62× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 287 rows 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. None are among the latest 100 rows. The 187 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 07:44 UTCEchelonGraph re-scored
  2. 2026-11-13 07:44 UTCGHSA enrichmentGHSA-494m-pv6g-vh73 · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-11-12 16:28 UTCEPSS rescoreEPSS 5.0% · 92nd percentile
  4. 2026-11-12 08:51 UTCEchelonGraph re-scored
  5. 2026-11-12 08:51 UTCGHSA enrichmentGHSA-494m-pv6g-vh73 · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-11-11 16:29 UTCEPSS rescoreEPSS 5.0% · 92nd percentile
  7. 2026-11-11 09:58 UTCEchelonGraph re-scored
  8. 2026-11-11 09:58 UTCVendor advisory
  9. 2026-11-11 09:58 UTCGHSA enrichmentGHSA-494m-pv6g-vh73 · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-11-10 16:31 UTCEPSS rescoreEPSS 5.0% · 92nd percentile
  11. 2026-11-10 11:05 UTCEchelonGraph re-scored
  12. 2026-11-10 11:05 UTCGHSA enrichmentGHSA-494m-pv6g-vh73 · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-11-09 16:27 UTCEPSS rescoreEPSS 5.0% · 92nd percentile
  14. 2026-11-09 12:12 UTCEchelonGraph re-scored
  15. 2026-11-09 12:12 UTCGHSA enrichmentGHSA-494m-pv6g-vh73 · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-11-08 16:30 UTCEPSS rescoreEPSS 5.0% · 92nd percentile
  17. 2026-11-08 13:20 UTCEchelonGraph re-scored
  18. 2026-11-08 13:20 UTCGHSA enrichmentGHSA-494m-pv6g-vh73 · GitHub severity CRITICAL · GitHub CVSS 9.8
  19. 2026-11-07 16:31 UTCEPSS rescoreEPSS 5.0% · 92nd percentile
  20. 2026-11-07 14:27 UTCEchelonGraph re-scored
  21. 2026-11-07 14:27 UTCGHSA enrichmentGHSA-494m-pv6g-vh73 · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-11-06 16:28 UTCEPSS rescoreEPSS 5.0% · 92nd percentile
  23. 2026-11-06 15:33 UTCGHSA enrichmentGHSA-494m-pv6g-vh73 · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-11-05 16:41 UTCEchelonGraph re-scored
  25. 2026-11-05 16:41 UTCGHSA enrichmentGHSA-494m-pv6g-vh73 · GitHub severity CRITICAL · GitHub CVSS 9.8
Show 75 more
  1. 2026-11-05 16:28 UTCEPSS rescoreEPSS 5.0% · 92nd percentile
  2. 2026-11-04 17:48 UTCEchelonGraph re-scored
  3. 2026-11-04 17:48 UTCGHSA enrichmentGHSA-494m-pv6g-vh73 · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-11-04 16:28 UTCEPSS rescoreEPSS 5.0% · 92nd percentile
  5. 2026-11-03 18:55 UTCEchelonGraph re-scored
  6. 2026-11-03 18:55 UTCGHSA enrichmentGHSA-494m-pv6g-vh73 · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-11-03 16:34 UTCEPSS rescoreEPSS 5.0% · 92nd percentile
  8. 2026-11-02 20:02 UTCEchelonGraph re-scored
  9. 2026-11-02 20:02 UTCGHSA enrichmentGHSA-494m-pv6g-vh73 · GitHub severity CRITICAL · GitHub CVSS 9.8
  10. 2026-11-02 18:25 UTCOSV refresh
  11. 2026-11-02 16:34 UTCEPSS rescoreEPSS 5.0% · 92nd percentile
  12. 2026-11-01 21:07 UTCEchelonGraph re-scored
  13. 2026-11-01 21:07 UTCGHSA enrichmentGHSA-494m-pv6g-vh73 · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-10-31 22:14 UTCEchelonGraph re-scored
  15. 2026-10-31 22:14 UTCGHSA enrichmentGHSA-494m-pv6g-vh73 · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-31 16:27 UTCEPSS rescoreEPSS 5.0% · 92nd percentile
  17. 2026-10-30 23:17 UTCEchelonGraph re-scored
  18. 2026-10-30 23:17 UTCGHSA enrichmentGHSA-494m-pv6g-vh73 · GitHub severity CRITICAL · GitHub CVSS 9.8
  19. 2026-10-30 16:28 UTCEPSS rescoreEPSS 5.0% · 92nd percentile
  20. 2026-10-30 00:24 UTCEchelonGraph re-scored
  21. 2026-10-30 00:24 UTCGHSA enrichmentGHSA-494m-pv6g-vh73 · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-10-29 16:28 UTCEPSS rescoreEPSS 5.0% · 92nd percentile
  23. 2026-10-29 01:32 UTCEchelonGraph re-scored
  24. 2026-10-29 01:32 UTCGHSA enrichmentGHSA-494m-pv6g-vh73 · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-10-28 16:27 UTCEPSS rescoreEPSS 5.0% · 92nd percentile
  26. 2026-10-28 02:40 UTCEchelonGraph re-scored
  27. 2026-10-28 02:39 UTCGHSA enrichmentGHSA-494m-pv6g-vh73 · GitHub severity CRITICAL · GitHub CVSS 9.8
  28. 2026-10-27 16:27 UTCEPSS rescoreEPSS 5.0% · 92nd percentile
  29. 2026-10-27 03:41 UTCEchelonGraph re-scored
  30. 2026-10-27 03:41 UTCGHSA enrichmentGHSA-494m-pv6g-vh73 · GitHub severity CRITICAL · GitHub CVSS 9.8
  31. 2026-10-26 16:26 UTCEPSS rescoreEPSS 5.0% · 92nd percentile
  32. 2026-10-26 00:36 UTCGHSA enrichmentGHSA-494m-pv6g-vh73 · GitHub severity CRITICAL · GitHub CVSS 9.8
  33. 2026-10-25 19:30 UTCEchelonGraph re-scored
  34. 2026-10-25 16:27 UTCEPSS rescoreEPSS 5.0% · 92nd percentile
  35. 2026-10-25 01:41 UTCEchelonGraph re-scored
  36. 2026-10-25 01:40 UTCGHSA enrichmentGHSA-494m-pv6g-vh73 · GitHub severity CRITICAL · GitHub CVSS 9.8
  37. 2026-10-24 16:27 UTCEPSS rescoreEPSS 5.0% · 92nd percentile
  38. 2026-10-24 02:48 UTCEchelonGraph re-scored
  39. 2026-10-24 02:48 UTCGHSA enrichmentGHSA-494m-pv6g-vh73 · GitHub severity CRITICAL · GitHub CVSS 9.8
  40. 2026-10-23 16:27 UTCEPSS rescoreEPSS 5.0% · 92nd percentile
  41. 2026-10-23 03:55 UTCEchelonGraph re-scored
  42. 2026-10-23 03:55 UTCGHSA enrichmentGHSA-494m-pv6g-vh73 · GitHub severity CRITICAL · GitHub CVSS 9.8
  43. 2026-10-22 16:27 UTCEPSS rescoreEPSS 5.0% · 92nd percentile
  44. 2026-10-22 05:02 UTCEchelonGraph re-scored
  45. 2026-10-22 05:01 UTCGHSA enrichmentGHSA-494m-pv6g-vh73 · GitHub severity CRITICAL · GitHub CVSS 9.8
  46. 2026-10-21 16:27 UTCEPSS rescoreEPSS 5.0% · 92nd percentile
  47. 2026-10-21 06:07 UTCEchelonGraph re-scored
  48. 2026-10-21 06:07 UTCGHSA enrichmentGHSA-494m-pv6g-vh73 · GitHub severity CRITICAL · GitHub CVSS 9.8
  49. 2026-10-20 16:27 UTCEPSS rescoreEPSS 5.0% · 92nd percentile
  50. 2026-10-20 07:11 UTCEchelonGraph re-scored
  51. 2026-10-20 07:11 UTCGHSA enrichmentGHSA-494m-pv6g-vh73 · GitHub severity CRITICAL · GitHub CVSS 9.8
  52. 2026-10-19 16:26 UTCEPSS rescoreEPSS 5.0% · 92nd percentile
  53. 2026-10-19 08:11 UTCEchelonGraph re-scored
  54. 2026-10-19 08:11 UTCGHSA enrichmentGHSA-494m-pv6g-vh73 · GitHub severity CRITICAL · GitHub CVSS 9.8
  55. 2026-10-18 16:27 UTCEPSS rescoreEPSS 5.0% · 92nd percentile
  56. 2026-10-18 09:13 UTCEchelonGraph re-scored
  57. 2026-10-18 09:13 UTCGHSA enrichmentGHSA-494m-pv6g-vh73 · GitHub severity CRITICAL · GitHub CVSS 9.8
  58. 2026-10-17 16:27 UTCEPSS rescoreEPSS 5.0% · 92nd percentile
  59. 2026-10-17 10:21 UTCEchelonGraph re-scored
  60. 2026-10-17 10:20 UTCGHSA enrichmentGHSA-494m-pv6g-vh73 · GitHub severity CRITICAL · GitHub CVSS 9.8
  61. 2026-10-16 16:29 UTCEPSS rescoreEPSS 5.0% · 92nd percentile
  62. 2026-10-16 11:26 UTCEchelonGraph re-scored
  63. 2026-10-16 11:26 UTCGHSA enrichmentGHSA-494m-pv6g-vh73 · GitHub severity CRITICAL · GitHub CVSS 9.8
  64. 2026-10-15 16:27 UTCEPSS rescoreEPSS 5.0% · 92nd percentile
  65. 2026-10-15 11:58 UTCEchelonGraph re-scored
  66. 2026-10-15 11:58 UTCGHSA enrichmentGHSA-494m-pv6g-vh73 · GitHub severity CRITICAL · GitHub CVSS 9.8
  67. 2026-10-14 16:27 UTCEPSS rescoreEPSS 5.0% · 92nd percentile
  68. 2026-10-14 07:30 UTCEchelonGraph re-scored
  69. 2026-10-14 07:29 UTCGHSA enrichmentGHSA-494m-pv6g-vh73 · GitHub severity CRITICAL · GitHub CVSS 9.8
  70. 2026-10-13 16:27 UTCEPSS rescoreEPSS 5.0% · 92nd percentile
  71. 2026-10-13 02:42 UTCGHSA enrichmentGHSA-494m-pv6g-vh73 · GitHub severity CRITICAL · GitHub CVSS 9.8
  72. 2026-10-12 20:25 UTCEchelonGraph re-scored
  73. 2026-10-12 16:28 UTCEPSS rescoreEPSS 5.0% · 92nd percentile
  74. 2026-10-12 00:48 UTCEchelonGraph re-scored
  75. 2026-10-11 13:41 UTCEPSS rescoreEPSS 5.0% · 92nd percentile

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 Exploit-DB entry). Defenders should treat patch urgency accordingly.

  • Exploit-DBEDB-41898✓ verified
    Published Apr 19, 2017

    Dmitry 1.3a - Local Buffer Overflow (PoC)

    Open source ↗

Related CVEs(same product + same vendor + same CWE)

Same product

2 shown

Debian:11:dmitry

Same vendor

1 shown

ubuntu:USN-8980-1

Frequently asked(5)

What is CVE-2017-7938?
CVE-2017-7938 is a critical-severity vulnerability; its CVE record was published on April 20, 2017. Stack-based buffer overflow in DMitry (Deepmagic Information Gathering Tool) version 1.3a (Unix) allows attackers to cause a denial of service (application crash) or possibly have unspecified other impact via a long argument. An example threat model is automated execution of DMitry with hostname…
When was CVE-2017-7938 made public?
CVE-2017-7938 was made public on April 20, 2017: that is the date its CVE record's CNA, MITRE Corporation, gives for when the vulnerability was made public. The CVE record itself was published on April 20, 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-7938 actively exploited?
CVE-2017-7938 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: Exploit-DB marks a public exploit for it as verified. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 5.0% probability of exploitation in the next 30 days (92nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2017-7938?
CVE-2017-7938 has a CVSS v3 base score of 6.6 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 9.8 (CRITICAL).
How do I remediate CVE-2017-7938?
A fix for CVE-2017-7938 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-7938

Explore →

Is Your Infrastructure Affected by CVE-2017-7938?

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

Book a Demo →Browse All CVEs