# CVE-2017-7938: Memory corruption in n/a

> Attackers can cause a crash or potentially execute code via a stack-based buffer overflow in DMitry when processing long arguments.

- **Severity:** Medium 6.6 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Apr 2017
- **Updated:** 3 Nov 2025
- **Also known as:** DEBIAN-CVE-2017-7938, GHSA-494m-pv6g-vh73, UBUNTU-CVE-2017-7938

## What is CVE-2017-7938?

CVE-2017-7938 is a medium-severity memory corruption vulnerability in n/a, published on 20 Apr 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2017-7938?

It affects 1 product.


Products: Mor-Pah.net Dmitry Deepmagic Information Gathering Tool.

## How do I fix CVE-2017-7938?

Apply the vendor's patch.

## Is CVE-2017-7938 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-7938 exists.

Public exploit code:

- Dmitry 1.3a - Local Buffer Overflow (PoC) (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-7938 and fix it if it is affected.

What it is: CVE-2017-7938 is a medium-severity memory corruption vulnerability in n/a, published on 20 Apr 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-7938 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-7938/ (Markdown: https://insights.sbomify.com/CVE-2017-7938/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-7938
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-7938
- OSV: https://osv.dev/vulnerability/CVE-2017-7938

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-7938/
Summaries are generated and may contain mistakes; the official description above is the record.