{"answers":{"affected":"2 open source packages ship an affected version, including pkg. It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-24828 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-24828 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-24828 is a medium-severity vulnerability in vercel pkg, published on 9 Feb 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-24828 and fix it if it is affected.\n\nWhat it is: CVE-2024-24828 is a medium-severity vulnerability in vercel pkg, published on 9 Feb 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-24828 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- pkg (npm): affected all versions up to 5.8.1; no fix listed\n- pkg (npm): affected all versions up to 5.8.1; no fix listed\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-24828/ (Markdown: https://insights.sbomify.com/CVE-2024-24828/index.md)","id":"CVE-2024-24828","markdown":"https://insights.sbomify.com/CVE-2024-24828/index.md","name":"CVE-2024-24828","record":{"aliases":["GHSA-22r3-9w55-cj54"],"analysis":{"component_type":"developer_tool","fix_type":"end_of_life","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Node.js bundler tool","requires_auth":"low_privilege","summary":"Local attackers can replace predictable native code files in a shared directory to execute malicious code when users run bundled executables.","user_interaction":"required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"pkg","vendor":"vercel"}],"cvss":{"score":6.6,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-276","name":"Incorrect Default Permissions"}],"description":"pkg is tool design to bundle Node.js projects into an executables. Any native code packages built by `pkg` are written to a hardcoded directory. On unix systems, this is `/tmp/pkg/*` which is a shared directory for all users on the same local system. There is no uniqueness to the package names within this directory, they are predictable. An attacker who has access to the same local system has the ability to replace the genuine executables in the shared directory with malicious executables of the same name. A user may then run the malicious executable without realising it has been modified. This package is deprecated. Therefore, there will not be a patch provided for this vulnerability. To check if your executable build by pkg depends on native code and is vulnerable, run the executable and check if `/tmp/pkg/` was created. Users should transition to actively maintained alternatives. We would recommend investigating Node.js 21’s support for single executable applications. Given the decision to deprecate the pkg package, there are no official workarounds or remediations provided by our team. Users should prioritize migrating to other packages that offer similar functionality with enhanced security.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Local Privilege Escalation in execuatables bundled by pkg","id":"CVE-2024-24828","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"privilege_escalation","year":"2024"},"n_packages":2,"n_references":2,"next":{"headline":"SSRF in Sentry via Phabricator integration","id":"CVE-2024-24829"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["5.8.1"],"package":"pkg","purl":null,"source":"GHSA-22r3-9w55-cj54"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["5.8.1"],"package":"pkg","purl":"pkg:npm/pkg","source":"GHSA-22r3-9w55-cj54"}],"prev":{"headline":"No rate limits on POST /uploads endpoint in Discourse","id":"CVE-2024-24827"},"products":["pkg"],"published":"2024-02-09","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-08-22","vendors":["vercel"]},"summary":"Local attackers can replace predictable native code files in a shared directory to execute malicious code when users run bundled executables.","url":"https://insights.sbomify.com/CVE-2024-24828/"}