# CVE-2001-0697: Denial of service in n/a

> Remote attackers can crash the NetWin SurgeFTP server by sending a specific directory listing command, requiring an upgrade to fix.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/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:** 9 Mar 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-vqw8-7vgj-vq9c

## What is CVE-2001-0697?

CVE-2001-0697 is a medium-severity denial of service vulnerability in n/a, published on 9 Mar 2002. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

NetWin SurgeFTP prior to 1.1h allows a remote attacker to cause a denial of service (crash) via an 'ls ..' command.

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

It affects 1 product.


Products: Netwin Surgeftp.

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

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

## Is CVE-2001-0697 being exploited?

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

Public exploit code:

- Netwin SurgeFTP 1.0b - Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2001-1356](https://insights.sbomify.com/CVE-2001-1356/): Weak cryptography in n/a (critical 10.0)
- [CVE-2007-3768](https://insights.sbomify.com/CVE-2007-3768/): Denial of service in n/a (high 8.5)
- [CVE-2013-4742](https://insights.sbomify.com/CVE-2013-4742/): Memory corruption in n/a (high 7.5)
- [CVE-2008-1052](https://insights.sbomify.com/CVE-2008-1052/): Null dereference in n/a (medium 6.4)
- [CVE-2017-17933](https://insights.sbomify.com/CVE-2017-17933/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2001-0697 is a medium-severity denial of service vulnerability in n/a, published on 9 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-0697 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-0697/ (Markdown: https://insights.sbomify.com/CVE-2001-0697/index.md)
```

## Sources

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

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