{"answers":{"affected":"2 open source packages ship an affected version, including bodymen. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-25296 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-25296 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-25296 is a medium-severity vulnerability in bodymen, published on 17 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-25296 and fix it if it is affected.\n\nWhat it is: CVE-2022-25296 is a medium-severity vulnerability in bodymen, published on 17 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-25296 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- bodymen (npm): affected from 0.0.0; no fix listed\n- bodymen (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/CVE-2022-25296/ (Markdown: https://insights.sbomify.com/CVE-2022-25296/index.md)","id":"CVE-2022-25296","markdown":"https://insights.sbomify.com/CVE-2022-25296/index.md","name":"CVE-2022-25296","record":{"aliases":["GHSA-vhxc-fhm5-qcp9"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js bodymen library","requires_auth":"low_privilege","summary":"Attackers can pollute Object.prototype via the handler function, potentially leading to code execution or security bypasses in applications using the bodymen library.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"snyk","cpe":[{"product":"bodymen","vendor":"bodymen_project"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:O/RC:C","version":"3.1"},"cwes":[{"id":"CWE-1321","name":"Improperly Controlled Modification of Object Prototype Attributes"}],"description":"The package bodymen from 0.0.0 are vulnerable to Prototype Pollution via the handler function which could be tricked into adding or modifying properties of Object.prototype using a __proto__ payload. **Note:** This vulnerability derives from an incomplete fix to [CVE-2019-10792](https://security.snyk.io/vuln/SNYK-JS-BODYMEN-548897)","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":"Prototype Pollution","id":"CVE-2022-25296","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"other","year":"2022"},"n_packages":2,"n_references":1,"next":{"headline":"Arbitrary File Write","id":"CVE-2022-25297"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0.0.0"],"last_affected":[],"package":"bodymen","purl":null,"source":"GHSA-vhxc-fhm5-qcp9"},{"ecosystem":"npm","fixed":[],"introduced":["0.0.0"],"last_affected":[],"package":"bodymen","purl":"pkg:npm/bodymen","source":"GHSA-vhxc-fhm5-qcp9"}],"prev":{"headline":"Open Redirect","id":"CVE-2022-25295"},"products":["bodymen"],"published":"2022-03-17","related":[{"cvss_score":6.3,"headline":"Injection in bodymen","id":"CVE-2019-10792","kev_date_added":null,"published":"2020-02-18"}],"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-17","vendors":["n/a"]},"summary":"Attackers can pollute Object.prototype via the handler function, potentially leading to code execution or security bypasses in applications using the bodymen library.","url":"https://insights.sbomify.com/CVE-2022-25296/"}