# CVE-2000-1033: Security feature bypass in n/a

> Remote attackers can bypass anti-hammering protections in Serv-U FTP Server by logging in as a valid user before guessing other passwords.

- **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:** 29 Nov 2000
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-9x63-cg6m-c448

## What is CVE-2000-1033?

CVE-2000-1033 is a high-severity vulnerability in n/a, published on 29 Nov 2000. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Serv-U FTP Server allows remote attackers to bypass its anti-hammering feature by first logging on as a valid user (possibly anonymous) and then attempting to guess the passwords of other users.

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

It affects 1 product.


Products: Cat Soft Serv-U.

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

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

## Is CVE-2000-1033 being exploited?

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

Public exploit code:

- Cat Soft Serv-U FTP Server 2.5.x - Brute Force (exploitdb)

## Other vulnerabilities in n/a

- [CVE-1999-0219](https://insights.sbomify.com/CVE-1999-0219/): Memory corruption in n/a (high 7.8)
- [CVE-2000-0176](https://insights.sbomify.com/CVE-2000-0176/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2000-1033 is a high-severity vulnerability in n/a, published on 29 Nov 2000. 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-2000-1033 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-2000-1033/ (Markdown: https://insights.sbomify.com/CVE-2000-1033/index.md)
```

## Sources

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

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