# CVE-2001-0376: Weak cryptography in n/a

> Remote attackers can brute force IKE pre-shared keys more easily due to truncated key length support in SonicWALL firewalls.

- **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:** 24 May 2001
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-wvm2-gmh5-gjgx

## What is CVE-2001-0376?

CVE-2001-0376 is a high-severity vulnerability in n/a, published on 24 May 2001. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SonicWALL Tele2 and SOHO firewalls with 6.0.0.0 firmware using IPSEC with IKE pre-shared keys do not allow for the use of full 128 byte IKE pre-shared keys, which is the intended design of the IKE pre-shared key, and only support 48 byte keys.  This allows a remote attacker to brute force attack the pre-shared keys with significantly less resources than if the full 128 byte IKE pre-shared keys were used.

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

It affects 2 products.


Products: Sonicwall Soho2, Sonicwall Tele2.

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

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

## Is CVE-2001-0376 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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