CVE-2001-1425
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe Alcatel Speed Touch router firmware versions KHDSAA.108 and KHDSAA.132 through KHDSAA.134 contains a flaw in the challenge-response authentication mechanism for the EXPERT user. The device provides information during the login process that allows remote attackers to directly compute the valid response, enabling privilege escalation without knowing the actual password.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= khdsaa.108= khdsaa.132= khdsaa.133= khdsaa.134CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the router's web interface or CLI and confirm the device is an Alcatel Speed Touch Home router. This is typically accessible via the router's IP address (often 10.0.0.1 or similar) in a web browser.Affected if The device is an Alcatel Speed Touch Home router
-
Retrieve the firmware versionIn the router's web interface, navigate to the status or system information page to view the firmware version. Alternatively, check the startup banner or version output via the console/Telnet interface.Affected if The displayed firmware version matches KHDSAA.108, KHDSAA.132, KHDSAA.133, or KHDSAA.134 exactly
-
Verify the EXPERT user is accessibleAttempt to log in to the router's web interface using the EXPERT user account. The vulnerability exists in the challenge-response mechanism for this privileged user account.Affected if The EXPERT user account exists and accepts authentication attempts
-
Confirm the authentication response behaviorDuring an EXPERT user login attempt, observe whether the device provides predictable challenge values that could be used to compute a valid response. This requires capturing the login sequence traffic or observing the authentication flow.Affected if The login process reveals challenge values that allow direct computation of the response without knowledge of the actual password
You are affected if you have an Alcatel Speed Touch Home router running firmware version KHDSAA.108, KHDSAA.132, KHDSAA.133, or KHDSAA.134 with the EXPERT user account accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to a newer firmware version if available from Alcatel; otherwise, replace the legacy device as this 2001-era hardware is likely end-of-life and no longer supported.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2001-1425 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2001-1425 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data