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

> Attackers can bypass authentication on HP AdvanceStack hubs to modify switch configurations and administrator passwords via direct HTTP requests.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/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:** 2 Apr 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-68r8-pmqw-v234

## What is CVE-2002-0250?

CVE-2002-0250 is a high-severity authentication bypass vulnerability in n/a, published on 2 Apr 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Web configuration utility in HP AdvanceStack hubs J3200A through J3210A with firmware version A.03.07 and earlier, allows unauthorized users to bypass authentication via a direct HTTP request to the web_access.html file, which allows the user to change the switch's configuration and modify the administrator password.

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

It affects 7 products.


Products: Hp Advancestack 10base-T Switching Hub J3200a, Hp Advancestack 10base-T Switching Hub J3201a, Hp Advancestack 10base-T Switching Hub J3202a, Hp Advancestack 10base-T Switching Hub J3203a, Hp Advancestack 10base-T Switching Hub J3204a, Hp Advancestack 10base-T Switching Hub J3205a, Hp Advancestack 10base-T Switching Hub J3210a.

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

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

## Is CVE-2002-0250 being exploited?

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

Public exploit code:

- HP AdvanceStack Switch - Authentication Bypass (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-0250 is a high-severity authentication bypass vulnerability in n/a, published on 2 Apr 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-0250 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-2002-0250/ (Markdown: https://insights.sbomify.com/CVE-2002-0250/index.md)
```

## Sources

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

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