{"answers":{"affected":"2 open source packages ship an affected version, including safe-eval.","exploited":"There is no known exploitation of GHSA-9pcf-h8q9-63f6 in the wild and no public exploit code.","fix":"No fix has been published for GHSA-9pcf-h8q9-63f6 yet. Limit exposure of the affected software until one is available.","what":"GHSA-9pcf-h8q9-63f6 is a code injection vulnerability in safe-eval, published on 3 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-9pcf-h8q9-63f6 and fix it if it is affected.\n\nWhat it is: GHSA-9pcf-h8q9-63f6 is a code injection vulnerability in safe-eval, published on 3 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-9pcf-h8q9-63f6 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- safe-eval (npm): affected from 0.0.0; no fix listed\n- safe-eval (npm): affected from 0.0.0; 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/GHSA-9pcf-h8q9-63f6/ (Markdown: https://insights.sbomify.com/GHSA-9pcf-h8q9-63f6/index.md)","id":"GHSA-9pcf-h8q9-63f6","markdown":"https://insights.sbomify.com/GHSA-9pcf-h8q9-63f6/index.md","name":"GHSA-9pcf-h8q9-63f6","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript sandbox library","requires_auth":"none","summary":"Attackers can escape the sandbox and execute arbitrary code via crafted payloads in the safe-eval library.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"All versions of `safe-eval` are vulnerable to Sandbox Escape leading to Remote Code Execution. A payload chaining a function's callee and caller constructors can escape the sandbox and execute arbitrary code.  \n\nFor example, the payload \n```\n((() =\u003e { \nconst targetKey = Object.keys(this)[0]; \nObject.defineProperty(this, targetKey, { \nget: function() { \nreturn arguments.callee.caller.constructor( \n\"return global.process.mainModule.require('child_process').execSync('pwd').toString()\" \n)(); \n} \n}); \n})();```\nmay be used to print the `pwd` to the console.\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.","ecosystems":["npm"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":false,"headline":"Sandbox Breakout / Arbitrary Code Execution in safe-eval","id":"GHSA-9pcf-h8q9-63f6","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2020"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0.0.0"],"last_affected":[],"package":"safe-eval","purl":null,"source":"GHSA-9pcf-h8q9-63f6"},{"ecosystem":"npm","fixed":[],"introduced":["0.0.0"],"last_affected":[],"package":"safe-eval","purl":"pkg:npm/safe-eval","source":"GHSA-9pcf-h8q9-63f6"}],"products":null,"published":"2020-09-03","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers can escape the sandbox and execute arbitrary code via crafted payloads in the safe-eval library.","url":"https://insights.sbomify.com/GHSA-9pcf-h8q9-63f6/"}