Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) Affecting npm package, versions <1:8.18.0-1.18.8.0.1.module+el8.7.0+20871+e727ae93


Severity

Recommended
high

Based on Oracle Linux security rating.

Threat Intelligence

EPSS
0.26% (66th 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-ORACLE8-NPM-3051690
  • published18 Oct 2022
  • disclosed5 Dec 2022

Introduced: 18 Oct 2022

CVE-2022-35255  (opens in a new tab)
CWE-338  (opens in a new tab)

How to fix?

Upgrade Oracle:8 npm to version 1:8.18.0-1.18.8.0.1.module+el8.7.0+20871+e727ae93 or higher.
This issue was patched in ELSA-2022-7821.

NVD Description

Note: Versions mentioned in the description apply only to the upstream npm package and not the npm package as distributed by Oracle. See How to fix? for Oracle: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