{"answers":{"affected":"2 open source packages ship an affected version, including node and node-min. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-30590 in the wild and no public exploit code.","fix":"Upgrade node to a fixed version for your release line: 16.20.1, 18.16.1 or 20.3.1.","what":"CVE-2023-30590 is a high-severity vulnerability in Nodejs Node.js, published on 28 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-30590 and fix it if it is affected.\n\nWhat it is: CVE-2023-30590 is a high-severity vulnerability in Nodejs Node.js, published on 28 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-30590 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- node (Bitnami): affected from 16.0.0; fixed in 16.20.1, 18.16.1, 20.3.1\n- node-min (Bitnami): affected from 16.0.0; fixed in 16.20.1, 18.16.1, 20.3.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-30590/ (Markdown: https://insights.sbomify.com/CVE-2023-30590/index.md)","id":"CVE-2023-30590","markdown":"https://insights.sbomify.com/CVE-2023-30590/index.md","name":"CVE-2023-30590","record":{"aliases":["BIT-node-2023-30590","BIT-node-min-2023-30590","DEBIAN-CVE-2023-30590","GHSA-v63h-9gvh-2x49","UBUNTU-CVE-2023-30590"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js crypto library","requires_auth":"none","summary":"Developers relying on Node.js Diffie-Hellman key generation may inadvertently use incomplete keys due to API behavior mismatching documentation, potentially weakening cryptographic security.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"node.js","vendor":"nodejs"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[],"description":"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\".\n\nThe 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.","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Other in Node","id":"CVE-2023-30590","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"nodejs:node.js","products":["nodejs:node.js"],"type":"other","year":"2023"},"n_packages":2,"n_references":2,"next":{"headline":"NodeBB Pre-Authentication Denial-of-Service","id":"CVE-2023-30591"},"packages":[{"ecosystem":"Bitnami","fixed":["16.20.1","18.16.1","20.3.1"],"introduced":["16.0.0","18.0.0","20.0.0"],"last_affected":[],"package":"node","purl":"pkg:bitnami/node","source":"BIT-node-2023-30590"},{"ecosystem":"Bitnami","fixed":["16.20.1","18.16.1","20.3.1"],"introduced":["16.0.0","18.0.0","20.0.0"],"last_affected":[],"package":"node-min","purl":"pkg:bitnami/node-min","source":"BIT-node-min-2023-30590"}],"prev":{"headline":"llhttp vulnerable to HTTP request smuggling","id":"CVE-2023-30589"},"products":["Node"],"published":"2023-11-28","related":[{"cvss_score":9.8,"headline":"Security feature bypass in Node","id":"CVE-2023-32002","kev_date_added":null,"published":"2023-08-21"},{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2016-6303","kev_date_added":null,"published":"2016-09-16"},{"cvss_score":9.1,"headline":"Security feature bypass in Node.js","id":"CVE-2017-15896","kev_date_added":null,"published":"2017-12-11"},{"cvss_score":8.8,"headline":"Server-side request forgery in Node.js","id":"CVE-2018-7160","kev_date_added":null,"published":"2018-05-17"},{"cvss_score":8.1,"headline":"Misconfiguration in Node.js","id":"CVE-2018-12120","kev_date_added":null,"published":"2018-11-28"},{"cvss_score":7.9,"headline":"Path traversal in Node","id":"CVE-2024-21891","kev_date_added":null,"published":"2024-02-20"},{"cvss_score":7.9,"headline":"Path traversal in Node","id":"CVE-2024-21896","kev_date_added":null,"published":"2024-02-20"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-08","vendors":["NodeJS"]},"summary":"Developers relying on Node.js Diffie-Hellman key generation may inadvertently use incomplete keys due to API behavior mismatching documentation, potentially weakening cryptographic security.","url":"https://insights.sbomify.com/CVE-2023-30590/"}