{"answers":{"affected":"2 open source packages ship an affected version, including safe-eval. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-16088 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-16088 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-16088 is a critical code injection vulnerability in HackerOne safe-eval node module, published on 7 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-16088 and fix it if it is affected.\n\nWhat it is: CVE-2017-16088 is a critical code injection vulnerability in HackerOne safe-eval node module, published on 7 Jun 2018. 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-2017-16088 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- safe-eval (npm): affected all versions up to 0.3.0; no fix listed\n- safe-eval (npm): affected all versions up to 0.3.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/CVE-2017-16088/ (Markdown: https://insights.sbomify.com/CVE-2017-16088/index.md)","id":"CVE-2017-16088","markdown":"https://insights.sbomify.com/CVE-2017-16088/index.md","name":"CVE-2017-16088","record":{"aliases":["GHSA-ww6v-677g-p656"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js safe-eval module","requires_auth":"none","summary":"Attackers can execute arbitrary code by accessing object constructors in the safe-eval Node.js module, bypassing its sandbox restrictions.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"safe-eval","vendor":"safe-eval_project"}],"cvss":{"score":10,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-610","name":"Externally Controlled Reference to a Resource in Another Sphere"}],"description":"The safe-eval module describes itself as a safer version of eval. By accessing the object constructors, un-sanitized user input can access the entire standard library and effectively break out of the sandbox.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":"2019-08-18","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2019-08-18T16:22:46Z","kind":"github_poc","ref":"https://github.com/Flyy-yu/CVE-2017-16088","stars":0,"title":"Exploit CVE-2017-16088 "}],"tier":"poc_unverified"},"has_fix":false,"headline":"Sandbox Breakout in safe-eval","id":"CVE-2017-16088","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2017"},"n_packages":2,"n_references":3,"next":{"headline":"Directory Traversal in serverlyr","id":"CVE-2017-16089"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.3.0"],"package":"safe-eval","purl":null,"source":"GHSA-ww6v-677g-p656"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.3.0"],"package":"safe-eval","purl":"pkg:npm/safe-eval","source":"GHSA-ww6v-677g-p656"}],"prev":{"headline":"ReDoS via long UserAgent header in ua-parser","id":"CVE-2017-16086"},"products":["safe-eval node module"],"published":"2018-06-07","related":[{"cvss_score":8.8,"headline":"safe-eval vulnerable to Sandbox Bypass due to improper input sanitization","id":"CVE-2023-26122","kev_date_added":null,"published":"2023-04-11"},{"cvss_score":8.1,"headline":"Sandbox Escape","id":"CVE-2020-7710","kev_date_added":null,"published":"2020-08-21"},{"cvss_score":7.5,"headline":"safe-eval vulnerable to Prototype Pollution via the safeEval function","id":"CVE-2023-26121","kev_date_added":null,"published":"2023-04-11"},{"cvss_score":7.5,"headline":"Prototype Pollution","id":"CVE-2022-25904","kev_date_added":null,"published":"2022-12-21"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["HackerOne"]},"summary":"Attackers can execute arbitrary code by accessing object constructors in the safe-eval Node.js module, bypassing its sandbox restrictions.","url":"https://insights.sbomify.com/CVE-2017-16088/"}