{"answers":{"affected":"2 open source packages ship an affected version, including safe-eval. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-25904 exists.","fix":"No fix has been published for CVE-2022-25904 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-25904 is a high-severity code injection vulnerability in safe-eval, published on 21 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-25904 and fix it if it is affected.\n\nWhat it is: CVE-2022-25904 is a high-severity code injection vulnerability in safe-eval, published on 21 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-25904 exists.\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-2022-25904/ (Markdown: https://insights.sbomify.com/CVE-2022-25904/index.md)","id":"CVE-2022-25904","markdown":"https://insights.sbomify.com/CVE-2022-25904/index.md","name":"CVE-2022-25904","record":{"aliases":["GHSA-33vh-7x8q-mg35"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript evaluation library","requires_auth":"none","summary":"Attackers can pollute Object.prototype via safeEval, potentially leading to code execution or privilege escalation in applications using this 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":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:P","version":"3.1"},"cwes":[{"id":"CWE-1321","name":"Improperly Controlled Modification of Object Prototype Attributes"}],"description":"All versions of package safe-eval are vulnerable to Prototype Pollution which allows an attacker to add or modify properties of the Object.prototype.Consolidate when using the function safeEval. This is because the function uses vm variable, leading an attacker to modify properties of the Object.prototype.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Prototype Pollution","id":"CVE-2022-25904","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2022"},"n_packages":2,"n_references":2,"next":{"headline":"Path traversal in Intel(R) oneAPI Data Analytics Library (oneDAL) for Intel(R) oneAPI Base Toolkit","id":"CVE-2022-25905"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.4.1"],"package":"safe-eval","purl":null,"source":"GHSA-33vh-7x8q-mg35"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.4.1"],"package":"safe-eval","purl":"pkg:npm/safe-eval","source":"GHSA-33vh-7x8q-mg35"}],"prev":{"headline":"Denial of Service (DoS)","id":"CVE-2022-25903"},"products":["safe-eval"],"published":"2022-12-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":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"}],"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":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-16","vendors":["n/a"]},"summary":"Attackers can pollute Object.prototype via safeEval, potentially leading to code execution or privilege escalation in applications using this library.","url":"https://insights.sbomify.com/CVE-2022-25904/"}