{"answers":{"affected":"2 open source packages ship an affected version, including node and node-min.","exploited":"There is no known exploitation of CVE-2024-22018 in the wild and no public exploit code.","fix":"Upgrade node to a fixed version for your release line: 20.15.1 or 22.4.1.","what":"CVE-2024-22018 is a low-severity vulnerability in NodeJS Node, published on 10 Jul 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-22018 and fix it if it is affected.\n\nWhat it is: CVE-2024-22018 is a low-severity vulnerability in NodeJS Node, published on 10 Jul 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-22018 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.15.1, 22.4.1\n- node-min (Bitnami): affected from 20.0.0; fixed in 20.18.1, 22.12.0\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-22018/ (Markdown: https://insights.sbomify.com/CVE-2024-22018/index.md)","id":"CVE-2024-22018","markdown":"https://insights.sbomify.com/CVE-2024-22018/index.md","name":"CVE-2024-22018","record":{"aliases":["ALPINE-CVE-2024-22018","AZL-43213","BELL-CVE-2024-22018","BIT-node-2024-22018","BIT-node-min-2024-22018","CLEANSTART-2026-SI30910","CLEANSTART-2026-XQ13634","DEBIAN-CVE-2024-22018","GHSA-9xvm-xmw3-2hm2","UBUNTU-CVE-2024-22018"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Node.js runtime","requires_auth":"none","summary":"Attackers can bypass file read restrictions to retrieve metadata from unauthorized files when using the experimental permission model in Node.js.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[],"cvss":{"score":2.9,"severity":"low","source":"cna","vector":"CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.0"},"cwes":[],"description":"A vulnerability has been identified in Node.js, affecting users of the experimental permission model when the --allow-fs-read flag is used.\nThis flaw arises from an inadequate permission model that fails to restrict file stats through the fs.lstat API. As a result, malicious actors can retrieve stats from files that they do not have explicit read access to.\nThis vulnerability affects all users using the experimental permission model in Node.js 20 and Node.js 21.\nPlease note that at the time this CVE was issued, the permission model is an experimental feature of Node.js.","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":"Information disclosure in Node","id":"CVE-2024-22018","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":2,"n_references":3,"next":{"headline":"Denial of service in Node","id":"CVE-2024-22019"},"packages":[{"ecosystem":"Bitnami","fixed":["20.15.1","22.4.1"],"introduced":["20.0.0","21.0.0"],"last_affected":[],"package":"node","purl":"pkg:bitnami/node","source":"BIT-node-2024-22018"},{"ecosystem":"Bitnami","fixed":["20.18.1","22.12.0"],"introduced":["20.0.0","21.0.0"],"last_affected":[],"package":"node-min","purl":"pkg:bitnami/node-min","source":"BIT-node-min-2024-22018"}],"prev":{"headline":"Privilege escalation in Node","id":"CVE-2024-22017"},"products":["Node"],"published":"2024-07-10","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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-30","vendors":["NodeJS"]},"summary":"Attackers can bypass file read restrictions to retrieve metadata from unauthorized files when using the experimental permission model in Node.js.","url":"https://insights.sbomify.com/CVE-2024-22018/"}