# CVE-2001-1112: Memory corruption in n/a

> Remote attackers can execute arbitrary code on EFTP servers by uploading a malicious .lnk file, requiring low privileges.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Mar 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-5554-grfx-fmf4

## What is CVE-2001-1112?

CVE-2001-1112 is a high-severity memory corruption vulnerability in n/a, published on 15 Mar 2002. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Buffer overflow in EFTP 2.0.7.337 allows remote attackers to execute arbitrary code by uploading a .lnk file containing a large number of characters.

## Which versions are affected by CVE-2001-1112?

It affects 1 product.


Products: Khamil Landross and Zack Jones Eftp.

## How do I fix CVE-2001-1112?

No fix has been published for CVE-2001-1112 yet. Limit exposure of the affected software until one is available.

## Is CVE-2001-1112 being exploited?

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

Public exploit code:

- EFTP 2.0.7 337 - Remote Buffer Overflow Code Execution / Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2001-1109](https://insights.sbomify.com/CVE-2001-1109/): Path traversal in n/a (high 7.5)
- [CVE-2000-0870](https://insights.sbomify.com/CVE-2000-0870/): Denial of service in n/a (high 7.5)
- [CVE-2001-1193](https://insights.sbomify.com/CVE-2001-1193/): Path traversal in n/a (medium 5.0)
- [CVE-2001-1110](https://insights.sbomify.com/CVE-2001-1110/): Information disclosure in n/a (medium 5.0)
- [CVE-2000-0871](https://insights.sbomify.com/CVE-2000-0871/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2001-1112 and fix it if it is affected.

What it is: CVE-2001-1112 is a high-severity memory corruption vulnerability in n/a, published on 15 Mar 2002. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2001-1112 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-2001-1112/ (Markdown: https://insights.sbomify.com/CVE-2001-1112/index.md)
```

## Sources

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

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