Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) Affecting nodejs:16/nodejs-devel package, versions <1:16.17.1-1.module+el8.6.0+16848+a483195a


Severity

Recommended
0.0
high
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.18% (57th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-RHEL8-NODEJS-4317487
  • published29 Sept 2022
  • disclosed23 Sept 2022

Introduced: 23 Sep 2022

CVE-2022-35255  (opens in a new tab)
CWE-338  (opens in a new tab)
First added by Snyk

How to fix?

Upgrade RHEL:8 nodejs:16/nodejs-devel to version 1:16.17.1-1.module+el8.6.0+16848+a483195a or higher.
This issue was patched in RHSA-2022:6964.

NVD Description

Note: Versions mentioned in the description apply only to the upstream nodejs:16/nodejs-devel package and not the nodejs:16/nodejs-devel package as distributed by RHEL. See How to fix? for RHEL:8 relevant fixed versions and status.

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.

CVSS Scores

version 3.1