{"answers":{"affected":"2 open source packages ship an affected version, including safer-eval. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-10769 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-10769 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-10769 is a critical code injection vulnerability in safer-eval, published on 6 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-10769 and fix it if it is affected.\n\nWhat it is: CVE-2019-10769 is a critical code injection vulnerability in safer-eval, published on 6 Dec 2019. 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-2019-10769 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- safer-eval (npm): affected all versions up to 1.3.6; no fix listed\n- safer-eval (npm): affected all versions up to 1.3.6; 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-2019-10769/ (Markdown: https://insights.sbomify.com/CVE-2019-10769/index.md)","id":"CVE-2019-10769","markdown":"https://insights.sbomify.com/CVE-2019-10769/index.md","name":"CVE-2019-10769","record":{"aliases":["GHSA-v63x-xc9j-hhvq"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js sandboxing library","requires_auth":"none","summary":"Attackers can execute arbitrary code by triggering a RangeError in the safer-eval sandbox, compromising applications using this Node.js library.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"snyk","cpe":[{"product":"safer-eval","vendor":"safer-eval_project"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"safer-eval is a npm package to sandbox the he evaluation of code used within the eval function. Affected versions of this package are vulnerable to Arbitrary Code Execution via generating a RangeError.","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 Breakout / Arbitrary Code Execution in safer-eval","id":"CVE-2019-10769","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2019"},"n_packages":2,"n_references":2,"next":{"headline":"Default development error handler in Ratpack is vulnerable to HTML content injection (XSS)","id":"CVE-2019-10770"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["1.3.6"],"package":"safer-eval","purl":null,"source":"GHSA-v63x-xc9j-hhvq"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["1.3.6"],"package":"safer-eval","purl":"pkg:npm/safer-eval","source":"GHSA-v63x-xc9j-hhvq"}],"prev":{"headline":"angular Prototype Pollution vulnerability","id":"CVE-2019-10768"},"products":["safer-eval"],"published":"2019-12-06","related":[{"cvss_score":9.9,"headline":"Sandbox Breakout / Arbitrary Code Execution in safer-eval","id":"CVE-2019-10759","kev_date_added":null,"published":"2019-10-15"},{"cvss_score":9.9,"headline":"Sandbox Breakout / Arbitrary Code Execution in safer-eval","id":"CVE-2019-10760","kev_date_added":null,"published":"2019-10-15"}],"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-08-04","vendors":["n/a"]},"summary":"Attackers can execute arbitrary code by triggering a RangeError in the safer-eval sandbox, compromising applications using this Node.js library.","url":"https://insights.sbomify.com/CVE-2019-10769/"}