LiveActive security incident?Get immediate response
CVE Record

CVE-2017-7938: Stack-based buffer overflow in DMitry (Deepmagic Information Gathering Tool) version 1.3a (Unix) allows att...

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.

MediumCVSS 6.6Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

DMitry 1.3a for Unix can crash when it receives an overly long argument. The main business risk is disruption of security or reconnaissance automation that runs DMitry on untrusted hostnames, such as strings pulled from logs. Limited confidentiality and integrity impact is also scored, but the source bundle does not prove remote compromise.

Executive priority

Treat as a moderate operational risk. Prioritize remediation where DMitry is automated, runs on shared systems, or processes untrusted data. Otherwise, handle through normal vulnerability maintenance and package update cycles.

Technical view

CVE-2017-7938 is a local stack-based buffer overflow in DMitry 1.3a. CVSS 3.1 is 6.6 with local attack vector, low complexity, low privileges, no user interaction, and high availability impact. Sources describe denial of service and possible unspecified impact via a long argument.

Likely exposure

Exposure is likely limited to Unix systems with DMitry 1.3a installed, especially scripts or batch jobs that pass untrusted hostname data into DMitry. Organizations not using DMitry, or using maintained distribution packages with relevant fixes, are less likely exposed.

Exploitation context

Public exploit references exist, including Exploit-DB, Packet Storm, and CXSecurity. The CVE is not marked KEV, and the provided sources do not show active exploitation. The example threat model is indirect local triggering through automated DMitry execution on hostile log-derived hostnames.

Researcher notes

Evidence supports DMitry 1.3a on Unix and a long-argument stack overflow. Public exploit listings increase validation urgency, but the bundle does not establish active exploitation, exact fixed upstream release, or affected downstream package ranges beyond cited advisories.

Mitigation direction

  • Inventory systems for DMitry 1.3a or vulnerable distribution packages.
  • Apply vendor or distribution updates, including relevant Debian LTS guidance where applicable.
  • Avoid passing untrusted hostname strings directly into DMitry automation.
  • Restrict who can run DMitry on shared Unix systems.
  • Sandbox or isolate jobs that process untrusted reconnaissance input.
  • Check upstream maintainer guidance before relying on source-level fixes.

Validation and detection

  • Confirm whether DMitry is installed and record the package or source version.
  • Review scheduled jobs and scripts that invoke DMitry automatically.
  • Verify patched package status against distribution security advisories.
  • Check logs for DMitry crashes during hostname or argument processing.
  • Confirm input validation exists before DMitry receives log-derived hostnames.
Prepared
Confidence
high
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2017-7938 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.6 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.6CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H1.84.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.6Medium
CVSS 3.1 vector shape for CVE-2017-7938Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.