Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) Affecting nodejs-debuginfo package, versions <1:18.12.1-1.amzn2023.0.2


Severity

Recommended
0.0
high
0
10

Based on Amazon 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-AMZN2023-NODEJSDEBUGINFO-3348522
  • published7 Mar 2023
  • disclosed5 Dec 2022

Introduced: 5 Dec 2022

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

How to fix?

Upgrade Amazon-Linux:2023 nodejs-debuginfo to version 1:18.12.1-1.amzn2023.0.2 or higher.
This issue was patched in ALAS2023-2023-084.

NVD Description

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