CVE-2023-30590 Affecting nodejs:16/nodejs-devel package, versions <1:16.20.2-2.module+el8.6.0+19897+9590a839


Severity

Recommended
0.0
high
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.08% (34th 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 IDSNYK-RHEL8-NODEJS-5920912
  • published6 Jul 2023
  • disclosed20 Jun 2023

Introduced: 20 Jun 2023

CVE-2023-30590  (opens in a new tab)
First added by Snyk

How to fix?

Upgrade RHEL:8 nodejs:16/nodejs-devel to version 1:16.20.2-2.module+el8.6.0+19897+9590a839 or higher.
This issue was patched in RHSA-2023:5361.

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.

The generateKeys() API function returned from crypto.createDiffieHellman() only generates missing (or outdated) keys, that is, it only generates a private key if none has been set yet, but the function is also needed to compute the corresponding public key after calling setPrivateKey(). However, the documentation says this API call: "Generates private and public Diffie-Hellman key values".

The documented behavior is very different from the actual behavior, and this difference could easily lead to security issues in applications that use these APIs as the DiffieHellman may be used as the basis for application-level security, implications are consequently broad.

CVSS Scores

version 3.1