# CVE-2008-1526: Weak cryptography in n/a

> Attackers can easily crack passwords because ZyXEL Prestige routers use unsalted MD5 hashes for password storage.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Mar 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-66rq-9hrq-6rw4

## What is CVE-2008-1526?

CVE-2008-1526 is a high-severity vulnerability in n/a, published on 26 Mar 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ZyXEL Prestige routers, including P-660, P-661, and P-662 models with firmware 3.40(PE9) and 3.40(AGD.2) through 3.40(AHQ.3), do not use a salt when calculating an MD5 password hash, which makes it easier for attackers to crack passwords.

Weakness: CWE-916 (Use of Password Hash With Insufficient Computational Effort)

## Which versions are affected by CVE-2008-1526?

It affects 19 products.


Products: Zyxel P-660h-61 Firmware, Zyxel P-660h-63 Firmware, Zyxel P-660h-67 Firmware, Zyxel P-660h-D1 Firmware, Zyxel P-660h-D3 Firmware, Zyxel P-660h-T1 Firmware, Zyxel P-660hn-51 Firmware, Zyxel P-660hw D1 Firmware, Zyxel P-660hw D3 Firmware, Zyxel P-660hw T3 Firmware, Zyxel P-661h Firmware, Zyxel P-661hnu-F1 Firmware, Zyxel P-661hnu-F3 Firmware, Zyxel P-661hw-D1 Firmware, Zyxel P-662h-61 Firmware, Zyxel P-662hw-D1 Firmware, Zyxel P-662hw-D3 Firmware, Zyxel P-662hw-D Firmware, Zyxel P-663hn-51 Firmware.

## How do I fix CVE-2008-1526?

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

## Is CVE-2008-1526 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-1526 and fix it if it is affected.

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

## Sources

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

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