CVE-2023-30590: 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...
High CVSS 7.5
- CVE id
- CVE-2023-30590
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| Node.js Runtimes and servers |
>= 16.0.0, < 16.20.1 >= 18.0.0, < 18.16.1 >= 20.0.0, < 20.3.1 |
16.20.1, 18.16.1, 20.3.1 |
How to fix it
Upgrade Node.js to the fixed release of the line you run: 16.20.1, 18.16.1, 20.3.1.
node --version
- Install the patched Node.js release of your major line (nvm install, or the node image tag) everywhere the app runs and builds.
A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.
Details
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.
References
- CVE-2023-30590 on the NVD
- Advisory: https://nvd.nist.gov/vuln/detail/CVE-2023-30590
- Web: https://lists.debian.org/debian-lts-announce/2024/03/msg00029.html
- Web: https://nodejs.org/en/blog/vulnerability/june-2023-security-releases
- Web: https://lists.debian.org/debian-lts-announce/2024/03/msg00029.html
- Web: https://lists.debian.org/debian-lts-announce/2024/09/msg00029.html
- Web: https://nodejs.org/en/blog/vulnerability/june-2023-security-releases
- Web: https://security.netapp.com/advisory/ntap-20241101-0011/
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.