# CVE-2022-35255: Weak cryptography in Node

> Weak randomness in Node.js WebCrypto keygen allows attackers to predict cryptographic keys, compromising security.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Dec 2022
- **Updated:** 30 Apr 2025
- **Also known as:** ALPINE-CVE-2022-35255, BIT-node-2022-35255, BIT-node-min-2022-35255, CLEANSTART-2026-DB79220, CLEANSTART-2026-IM09433, DEBIAN-CVE-2022-35255, GHSA-p36x-w6hr-88jp

## What is CVE-2022-35255?

CVE-2022-35255 is a critical vulnerability in Debian Debian Linux, published on 5 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A weak randomness in WebCrypto keygen vulnerability exists in Node.js 18 due to a change with EntropySource() in SecretKeyGenTraits::DoKeyGen() in src/crypto/crypto_keygen.cc. There are two problems with this: 1) It does not check the return value, it assumes EntropySource() always succeeds, but it can (and sometimes will) fail. 2) The random data returned byEntropySource() may not be cryptographically strong and therefore not suitable as keying material.

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

## Which versions are affected by CVE-2022-35255?

2 open source packages ship an affected version, including node and node-min. It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `node` | Bitnami | From 15.0.0 | 15.14.1, 16.12.1, 16.17.1, 18.9.1 |
| `node-min` | Bitnami | From 15.0.0 | 15.14.1, 16.12.1, 16.17.1, 18.9.1 |

Products: Debian Debian Linux, Nodejs Node.js, Siemens Sinec Ins.

## How do I fix CVE-2022-35255?

Upgrade node to a fixed version for your release line: 15.14.1, 16.12.1, 16.17.1 or 18.9.1.

## Is CVE-2022-35255 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-35255 and fix it if it is affected.

What it is: CVE-2022-35255 is a critical vulnerability in Debian Debian Linux, published on 5 Dec 2022. 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-2022-35255 in the wild and no public exploit code.

Affected packages and fixed versions:
- node (Bitnami): affected from 15.0.0; fixed in 15.14.1, 16.12.1, 16.17.1, 18.9.1
- node-min (Bitnami): affected from 15.0.0; fixed in 15.14.1, 16.12.1, 16.17.1, 18.9.1

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-2022-35255/ (Markdown: https://insights.sbomify.com/CVE-2022-35255/index.md)
```

## Sources

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

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