# CVE-2001-1425: Auth bypass in n/a

> Remote attackers can bypass authentication and gain privileges on Alcatel Speed Touch devices by computing the challenge-response login token.

- **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:** 22 Mar 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-jrx8-7v63-j3rx

## What is CVE-2001-1425?

CVE-2001-1425 is a high-severity authentication bypass vulnerability in n/a, published on 22 Mar 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The challenge-response authentication of the EXPERT user for Alcatel Speed Touch running firmware KHDSAA.108 and KHDSAA.132 through KHDSAA.134 allows remote attackers to gain privileges by directly computing the response based on information that is provided by the device during login.

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

It affects 1 product.


Products: Alcatel Speed Touch Home.

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

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

## Is CVE-2001-1425 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2001-1424](https://insights.sbomify.com/CVE-2001-1424/): Hardcoded credentials in n/a (high 7.5)
- [CVE-2001-1426](https://insights.sbomify.com/CVE-2001-1426/): Missing authorization in n/a (high 7.5)
- [CVE-2002-0119](https://insights.sbomify.com/CVE-2002-0119/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2001-1425 is a high-severity authentication bypass vulnerability in n/a, published on 22 Mar 2005. 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-1425 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-1425/ (Markdown: https://insights.sbomify.com/CVE-2001-1425/index.md)
```

## Sources

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

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