# CVE-2000-0871: Denial of service in n/a

> Remote attackers can cause a denial of service in EFTP by sending a string without a newline and disconnecting.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jan 2001
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-gg4h-2f4h-wg43

## What is CVE-2000-0871?

CVE-2000-0871 is a medium-severity denial of service vulnerability in n/a, published on 22 Jan 2001. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in EFTP allows remote attackers to cause a denial of service by sending a string that does not contain a newline, then disconnecting from the server.

## Which versions are affected by CVE-2000-0871?

It affects 1 product.


Products: Khamil Landross and Zack Jones Eftp.

## How do I fix CVE-2000-0871?

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

## Is CVE-2000-0871 being exploited?

There is no known exploitation of CVE-2000-0871 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2001-1109](https://insights.sbomify.com/CVE-2001-1109/): Path traversal in n/a (high 7.5)
- [CVE-2001-1112](https://insights.sbomify.com/CVE-2001-1112/): Memory corruption 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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2000-0871 and fix it if it is affected.

What it is: CVE-2000-0871 is a medium-severity denial of service vulnerability in n/a, published on 22 Jan 2001. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2000-0871 in the wild and no public exploit code.

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-2000-0871/ (Markdown: https://insights.sbomify.com/CVE-2000-0871/index.md)
```

## Sources

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

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