# CVE-2001-1356: Weak cryptography in n/a

> Weak password hashing in NetWin SurgeFTP allows remote attackers to brute force administrator credentials and gain unauthorized access.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jun 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-cq9x-572j-h52j

## What is CVE-2001-1356?

CVE-2001-1356 is a critical vulnerability in n/a, published on 11 Jun 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NetWin SurgeFTP 2.0f and earlier encrypts passwords using weak hashing, a fixed salt value and modulo 40 calculations, which allows remote attackers to conduct brute force password guessing attacks against the administrator account on port 7021.

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

It affects 1 product.


Products: Netwin Surgeftp.

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

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

## Is CVE-2001-1356 being exploited?

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

## Other vulnerabilities in n/a

- [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)
- [CVE-2007-3769](https://insights.sbomify.com/CVE-2007-3769/): Cross-site scripting in n/a (medium 5.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2001-1356 is a critical vulnerability in n/a, published on 11 Jun 2002. 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-2001-1356 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-2001-1356/ (Markdown: https://insights.sbomify.com/CVE-2001-1356/index.md)
```

## Sources

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

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