CVE-2023-30590: The generateKeys() API function returned from crypto.createDiffieHellman() only generates missing (or outdated) keys, that is, it only…
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.4% (FIRST EPSS); higher than 74% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: NodeJS Node 10.*, 11.*, 12.*.
Low priority for now. Upgrade to NodeJS Node 10.*, 11.*, 12.* or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- BDU:2023-04930
- ALSA-2023:4330
- ALSA-2023:4331
- ALSA-2023:4536
- ALSA-2023:4537
- DLA-3776-1
- DLA-3886-1
- DSA-5589-1
- openSUSE-SU-2024:13021-1
- RHSA-2023:4330
- RHSA-2023:4331
- RHSA-2023:4536
- RHSA-2023:4537
- RHSA-2023:5361
- RHSA-2023:5533
- RLSA-2023:4330
- RLSA-2023:4536
- RLSA-2023:4537
- SUSE-SU-2023:2655-1
- SUSE-SU-2023:2662-1
- Published
- Nov 28, 2023
- Updated
- Oct 8, 2026
- EPSS
- 1.4% · 74th percentile
- CWE
- —
Report tools
Action score
30
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| nodejs | node.js | cpe:2.3:a:nodejs:node.js |
Using node.js? Add it to your stack and be the first to know about CVEs like this one. (Node.js)
Versions reported by the vendor
Affected version ranges reported by the assigning authority (hackerone). Independent of NVD's CPE analysis and usually ahead of it.
NodeJS Node
- 4.0 and later · before 4.*affected · semver
- 5.0 and later · before 5.*affected · semver
- 6.0 and later · before 6.*affected · semver
- 7.0 and later · before 7.*affected · semver
- 8.0 and later · before 8.*affected · semver
- 9.0 and later · before 9.*affected · semver
- 10.0 and later · before 10.*affected · semver
- 11.0 and later · before 11.*affected · semver
- 12.0 and later · before 12.*affected · semver
- 13.0 and later · before 13.*affected · semver
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- nodejs node.js16.0.0 and later · before 16.20.1
- nodejs node.js18.0.0 and later · before 18.16.1
- nodejs node.js20.0.0 and later · before 20.3.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | nodejs | before 1:16.20.1-1.module_el8.8.0+3594+e74fe53f | 1:16.20.1-1.module_el8.8.0+3594+e74fe53f |
| AlmaLinux:8 | nodejs | before 1:18.16.1-1.module_el8.8.0+3595+0818e803 | 1:18.16.1-1.module_el8.8.0+3595+0818e803 |
| AlmaLinux:8 | nodejs-devel | before 1:16.20.1-1.module_el8.8.0+3594+e74fe53f | 1:16.20.1-1.module_el8.8.0+3594+e74fe53f |
| AlmaLinux:8 | nodejs-devel | before 1:18.16.1-1.module_el8.8.0+3595+0818e803 | 1:18.16.1-1.module_el8.8.0+3595+0818e803 |
| AlmaLinux:8 | nodejs-docs | before 1:16.20.1-1.module_el8.8.0+3594+e74fe53f | 1:16.20.1-1.module_el8.8.0+3594+e74fe53f |
| AlmaLinux:8 | nodejs-docs | before 1:18.16.1-1.module_el8.8.0+3595+0818e803 | 1:18.16.1-1.module_el8.8.0+3595+0818e803 |
| AlmaLinux:8 | nodejs-full-i18n | before 1:16.20.1-1.module_el8.8.0+3594+e74fe53f | 1:16.20.1-1.module_el8.8.0+3594+e74fe53f |
| AlmaLinux:8 | nodejs-full-i18n | before 1:18.16.1-1.module_el8.8.0+3595+0818e803 | 1:18.16.1-1.module_el8.8.0+3595+0818e803 |
| AlmaLinux:8 | nodejs-nodemon | before 2.0.20-2.module_el8.8.0+3587+ee652244 | 2.0.20-2.module_el8.8.0+3587+ee652244 |
| AlmaLinux:8 | nodejs-nodemon | before 2.0.20-3.module_el8.8.0+3586+d4fc0b72 | 2.0.20-3.module_el8.8.0+3586+d4fc0b72 |
| AlmaLinux:8 | nodejs-packaging | before 2021.06-4.module_el8.7.0+3343+ea2b7901 | 2021.06-4.module_el8.7.0+3343+ea2b7901 |
| AlmaLinux:8 | nodejs-packaging | before 25-1.module_el8.5.0+2605+45d748af | 25-1.module_el8.5.0+2605+45d748af |
| AlmaLinux:8 | nodejs-packaging-bundler | before 2021.06-4.module_el8.7.0+3343+ea2b7901 | 2021.06-4.module_el8.7.0+3343+ea2b7901 |
| AlmaLinux:8 | npm | before 1:8.19.4-1.16.20.1.1.module_el8.8.0+3594+e74fe53f | 1:8.19.4-1.16.20.1.1.module_el8.8.0+3594+e74fe53f |
| AlmaLinux:8 | npm | before 1:9.5.1-1.18.16.1.1.module_el8.8.0+3595+0818e803 | 1:9.5.1-1.18.16.1.1.module_el8.8.0+3595+0818e803 |
| AlmaLinux:9 | nodejs | before 1:16.20.1-1.el9_2 | 1:16.20.1-1.el9_2 |
| AlmaLinux:9 | nodejs | before 1:18.16.1-1.module_el9.2.0+31+cbae0c8e | 1:18.16.1-1.module_el9.2.0+31+cbae0c8e |
| AlmaLinux:9 | nodejs-devel | before 1:18.16.1-1.module_el9.2.0+31+cbae0c8e | 1:18.16.1-1.module_el9.2.0+31+cbae0c8e |
| AlmaLinux:9 | nodejs-docs | before 1:16.20.1-1.el9_2 | 1:16.20.1-1.el9_2 |
| AlmaLinux:9 | nodejs-docs | before 1:18.16.1-1.module_el9.2.0+31+cbae0c8e | 1:18.16.1-1.module_el9.2.0+31+cbae0c8e |
| AlmaLinux:9 | nodejs-full-i18n | before 1:16.20.1-1.el9_2 | 1:16.20.1-1.el9_2 |
| AlmaLinux:9 | nodejs-full-i18n | before 1:18.16.1-1.module_el9.2.0+31+cbae0c8e | 1:18.16.1-1.module_el9.2.0+31+cbae0c8e |
| AlmaLinux:9 | nodejs-libs | before 1:16.20.1-1.el9_2 | 1:16.20.1-1.el9_2 |
| AlmaLinux:9 | nodejs-nodemon | before 2.0.20-2.module_el9.2.0+29+de583a0b | 2.0.20-2.module_el9.2.0+29+de583a0b |
+81
Same product
nodejs: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-15605HTTP request smuggling in Node.js 10, 12, and 13 causes malicious payload delivery when transfer-encoding is malformed56Plan
- CVE-2021-22883Node.js before 10.24.0, 12.21.0, 14.16.0, and 15.10.0 is vulnerable to a denial of service attack when too many connection attempts with an…53Plan
- CVE-2021-22930Node.js before 16.6.0, 14.17.4, and 12.22.4 is vulnerable to a use after free attack where an attacker might be able to exploit the memory…50Plan
Published before and after this one in the same product
- ← EarlierCVE-2023-30585Nov 28, 2023 · A vulnerability has been identified in the Node.js (.msi version) installation process, specifically affecting Windows users who install…30Monitor
- ← EarlierCVE-2023-30588Nov 28, 2023 · When an invalid public key is used to create an x509 certificate using the crypto.X509Certificate() API a non-expect termination occurs…21Monitor
- Later →CVE-2024-21890Feb 19, 2024 · The Node.js Permission Model does not clarify in the documentation that wildcards should be only used as the last character of a file path.26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| NodeJS Node | 10.* | Vendor (CNA) |
| NodeJS Node | 11.* | Vendor (CNA) |
| NodeJS Node | 12.* | Vendor (CNA) |
| NodeJS Node | 13.* | Vendor (CNA) |
| NodeJS Node | 14.* | Vendor (CNA) |
| NodeJS Node | 15.* | Vendor (CNA) |
| NodeJS Node | 16.20.1 | Vendor (CNA) |
| NodeJS Node | 17.* | Vendor (CNA) |
| NodeJS Node | 18.16.1 | Vendor (CNA) |
| NodeJS Node | 19.* | Vendor (CNA) |
| NodeJS Node | 20.3.1 | Vendor (CNA) |
| NodeJS Node | 4.* | Vendor (CNA) |
| NodeJS Node | 5.* | Vendor (CNA) |
| NodeJS Node | 6.* | Vendor (CNA) |
| NodeJS Node | 7.* | Vendor (CNA) |
| NodeJS Node | 8.* | Vendor (CNA) |
| NodeJS Node | 9.* | Vendor (CNA) |
| almalinux:nodejs | 1:18.16.1-1.module_el9.2.0+31+cbae0c8e · AlmaLinux:9 | Package registry (OSV) |
| almalinux:nodejs-devel | 1:18.16.1-1.module_el9.2.0+31+cbae0c8e · AlmaLinux:9 | Package registry (OSV) |
| almalinux:nodejs-docs | 1:18.16.1-1.module_el9.2.0+31+cbae0c8e · AlmaLinux:9 | Package registry (OSV) |
| almalinux:nodejs-full-i18n | 1:18.16.1-1.module_el9.2.0+31+cbae0c8e · AlmaLinux:9 | Package registry (OSV) |
| almalinux:nodejs-libs | 1:16.20.1-1.el9_2 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:nodejs-nodemon | 2.0.20-2.module_el9.2.0+29+de583a0b · AlmaLinux:9 | Package registry (OSV) |
| almalinux:nodejs-packaging | 2021.06-4.module_el9.1.0+13+d9a595ea · AlmaLinux:9 | Package registry (OSV) |
| almalinux:nodejs-packaging-bundler | 2021.06-4.module_el9.1.0+13+d9a595ea · AlmaLinux:9 | Package registry (OSV) |
| almalinux:npm | 1:9.5.1-1.18.16.1.1.module_el9.2.0+31+cbae0c8e · AlmaLinux:9 | Package registry (OSV) |
| debian:nodejs | 18.19.0+dfsg-6~deb12u1 · Debian:12 | Package registry (OSV) |
| opensuse:nodejs12 | 12.22.12-150200.4.50.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| opensuse:nodejs14 | 14.21.3-150200.15.49.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| opensuse:nodejs16 | 16.20.1-150400.3.21.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
+25
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.