{"answers":{"affected":"2 open source packages ship an affected version, including node and node-min.","exploited":"There is no known exploitation of CVE-2024-22017 in the wild and no public exploit code.","fix":"Upgrade node to a fixed version for your release line: 20.11.1 or 21.6.2.","what":"CVE-2024-22017 is a high-severity vulnerability in NodeJS Node, published on 19 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-22017 and fix it if it is affected.\n\nWhat it is: CVE-2024-22017 is a high-severity vulnerability in NodeJS Node, published on 19 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-22017 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- node (Bitnami): affected from 20.0.0; fixed in 20.11.1, 21.6.2\n- node-min (Bitnami): affected from 20.0.0; fixed in 20.11.1, 21.6.2\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-2024-22017/ (Markdown: https://insights.sbomify.com/CVE-2024-22017/index.md)","id":"CVE-2024-22017","markdown":"https://insights.sbomify.com/CVE-2024-22017/index.md","name":"CVE-2024-22017","record":{"aliases":["AZL-35886","AZL-35899","BELL-CVE-2024-22017","BIT-node-2024-22017","BIT-node-min-2024-22017","GHSA-vr4q-vx84-9g5x","openSUSE-SU-2024:13972-1"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Node.js runtime","requires_auth":"high_privilege","summary":"Attackers can retain privileged operations after dropping privileges via setuid() if libuv io_uring was initialized earlier, leading to privilege escalation in Node.js applications.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:C/C:L/I:H/A:L","version":"3.0"},"cwes":[{"id":"CWE-250","name":"Execution with Unnecessary Privileges"}],"description":"setuid() does not affect libuv's internal io_uring operations if initialized before the call to setuid().\nThis allows the process to perform privileged operations despite presumably having dropped such privileges through a call to setuid().\nThis vulnerability affects all users using version greater or equal than Node.js 18.18.0, Node.js 20.4.0 and Node.js 21.","ecosystems":["Bitnami","openSUSE:Tumbleweed"],"exploits":{"exploitdb":0,"first_seen":"2025-01-12","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-01-12T13:40:16Z","kind":"github_poc","ref":"https://github.com/SpiralBL0CK/cve-2024-22017_to_test","stars":0,"title":null}],"tier":"poc_unverified"},"has_fix":true,"headline":"Privilege escalation in Node","id":"CVE-2024-22017","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"privilege_escalation","year":"2024"},"n_packages":3,"n_references":3,"next":{"headline":"Information disclosure in Node","id":"CVE-2024-22018"},"packages":[{"ecosystem":"Bitnami","fixed":["20.11.1","21.6.2"],"introduced":["20.0.0","21.0.0"],"last_affected":[],"package":"node","purl":"pkg:bitnami/node","source":"BIT-node-2024-22017"},{"ecosystem":"Bitnami","fixed":["20.11.1","21.6.2"],"introduced":["20.0.0","21.0.0"],"last_affected":[],"package":"node-min","purl":"pkg:bitnami/node-min","source":"BIT-node-min-2024-22017"},{"ecosystem":"openSUSE:Tumbleweed","fixed":["29.4.0-1.1"],"introduced":["0"],"last_affected":[],"package":"nodejs-electron","purl":"pkg:rpm/opensuse/nodejs-electron\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2024:13972-1"}],"prev":{"headline":"Incorrect Permission Assignment for Critical Resource in Rapid SCADA","id":"CVE-2024-22016"},"products":["Node"],"published":"2024-03-19","related":[],"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":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-30","vendors":["NodeJS"]},"summary":"Attackers can retain privileged operations after dropping privileges via setuid() if libuv io_uring was initialized earlier, leading to privilege escalation in Node.js applications.","url":"https://insights.sbomify.com/CVE-2024-22017/"}