# CVE-2024-40762: Weak cryptography in SonicOS

> Attackers can predict SSLVPN authentication tokens due to weak PRNG usage, potentially bypassing authentication on SonicWall devices.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jan 2025
- **Updated:** 9 Jan 2025
- **Also known as:** GHSA-cpr8-m35v-9vv2

## What is CVE-2024-40762?

CVE-2024-40762 is a critical vulnerability in SonicWall SonicOS, published on 9 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) in the SonicOS SSLVPN authentication token generator that, in certain cases, can be predicted by an attacker potentially resulting in authentication bypass.

Weakness: CWE-338 (Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG))

## Which versions are affected by CVE-2024-40762?


## How do I fix CVE-2024-40762?

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

## Is CVE-2024-40762 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-40762 and fix it if it is affected.

What it is: CVE-2024-40762 is a critical vulnerability in SonicWall SonicOS, published on 9 Jan 2025. 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-2024-40762 in the wild and no public exploit code.

Affected product: SonicWall SonicOS. 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-2024-40762/ (Markdown: https://insights.sbomify.com/CVE-2024-40762/index.md)
```

## Sources

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

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