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.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2023-30590US | high7.5OT elevated | — | ||
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… | ||||
references
External citations — patches, advisories, analysis.
- https://lists.debian.org/debian-lts-announce/2024/03/msg00029.htmlWEB
- https://lists.debian.org/debian-lts-announce/2024/09/msg00029.htmlWEB
- https://nodejs.org/en/blog/vulnerability/june-2023-security-releasesADVISORY
- https://nvd.nist.gov/vuln/detail/CVE-2023-30590WEB
- https://security.netapp.com/advisory/ntap-20241101-0011/WEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan