# CVE-2007-2332: Weak cryptography in n/a

> Remote authenticated users can recover passwords via brute force due to a fixed DES key used for encryption in Nortel VPN Routers.

- **Severity:** Critical 9.0 (`AV:N/AC:L/Au:S/C:C/I:C/A:C`)
- **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:** 27 Apr 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4qc5-qj4v-hc88

## What is CVE-2007-2332?

CVE-2007-2332 is a critical vulnerability in n/a, published on 27 Apr 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Nortel VPN Router (aka Contivity) 1000, 2000, 4000, and 5000 before 6_05.140 uses a fixed DES key to encrypt passwords, which allows remote authenticated users to obtain a password via a brute force attack on a hash from the LDAP store.

## Which versions are affected by CVE-2007-2332?

It affects 8 products.


Products: Nortel Vpn Router 1010, Nortel Vpn Router 1050, Nortel Vpn Router 1100, Nortel Vpn Router 1700, Nortel Vpn Router 1740, Nortel Vpn Router 1750, Nortel Vpn Router 2700, Nortel Vpn Router 5000.

## How do I fix CVE-2007-2332?

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

## Is CVE-2007-2332 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-2332 and fix it if it is affected.

What it is: CVE-2007-2332 is a critical vulnerability in n/a, published on 27 Apr 2007. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-2332 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-2007-2332/ (Markdown: https://insights.sbomify.com/CVE-2007-2332/index.md)
```

## Sources

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

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