{"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-2020-7710 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-7710 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-7710 is a high-severity code injection vulnerability in safe-eval, published on 21 Aug 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-7710 and fix it if it is affected.\n\nWhat it is: CVE-2020-7710 is a high-severity code injection vulnerability in safe-eval, published on 21 Aug 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 CVE-2020-7710 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- safe-eval (npm): affected all versions up to 0.4.1; no fix listed\n- safe-eval (npm): affected all versions up to 0.4.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-2020-7710/ (Markdown: https://insights.sbomify.com/CVE-2020-7710/index.md)","id":"CVE-2020-7710","markdown":"https://insights.sbomify.com/CVE-2020-7710/index.md","name":"CVE-2020-7710","record":{"aliases":["GHSA-hrpq-r399-whgw"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js safe-eval library","requires_auth":"none","summary":"An attacker can execute arbitrary commands on the host machine by exploiting a sandbox escape vulnerability in the safe-eval library.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"snyk","cpe":[{"product":"safe-eval","vendor":"safe-eval_project"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:U/RC:C","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"This affects all versions of package safe-eval. It is possible for an attacker to run an arbitrary command on the host machine.","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":"Sandbox Escape","id":"CVE-2020-7710","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2020"},"n_packages":2,"n_references":2,"next":{"headline":"Denial of Service (DoS)","id":"CVE-2020-7711"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.4.1"],"package":"safe-eval","purl":null,"source":"GHSA-hrpq-r399-whgw"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.4.1"],"package":"safe-eval","purl":"pkg:npm/safe-eval","source":"GHSA-hrpq-r399-whgw"}],"prev":{"headline":"Prototype Pollution","id":"CVE-2020-7709"},"products":["safe-eval"],"published":"2020-08-21","related":[{"cvss_score":10,"headline":"Sandbox Breakout in safe-eval","id":"CVE-2017-16088","kev_date_added":null,"published":"2018-06-07"},{"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":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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["n/a"]},"summary":"An attacker can execute arbitrary commands on the host machine by exploiting a sandbox escape vulnerability in the safe-eval library.","url":"https://insights.sbomify.com/CVE-2020-7710/"}