# CVE-2002-1047: Auth bypass in n/a

> Remote attackers can gain privileges on Watchguard Soho Firewall by using a correct password with an incorrect username.

- **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:** 31 Aug 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-6pjp-9q5v-gp94

## What is CVE-2002-1047?

CVE-2002-1047 is a high-severity authentication bypass vulnerability in n/a, published on 31 Aug 2002. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The FTP service in Watchguard Soho Firewall 5.0.35a allows remote attackers to gain privileges with a correct password but an incorrect user name.

## Which versions are affected by CVE-2002-1047?

It affects 1 product.


Products: Watchguard Soho Firewall.

## How do I fix CVE-2002-1047?

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

## Is CVE-2002-1047 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2000-0894](https://insights.sbomify.com/CVE-2000-0894/): Missing authorization in n/a (critical 10.0)
- [CVE-2000-0895](https://insights.sbomify.com/CVE-2000-0895/): Memory corruption in n/a (critical 10.0)
- [CVE-2002-0528](https://insights.sbomify.com/CVE-2002-0528/): Security feature bypass in n/a (critical 10.0)
- [CVE-2002-0527](https://insights.sbomify.com/CVE-2002-0527/): Denial of service in n/a (medium 5.0)
- [CVE-2000-0896](https://insights.sbomify.com/CVE-2000-0896/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-1047 and fix it if it is affected.

What it is: CVE-2002-1047 is a high-severity authentication bypass vulnerability in n/a, published on 31 Aug 2002. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2002-1047 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-2002-1047/ (Markdown: https://insights.sbomify.com/CVE-2002-1047/index.md)
```

## Sources

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

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