{"answers":{"affected":"2 open source packages ship an affected version, including bwm-ng. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-26129 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-26129 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-26129 is a high-severity command injection vulnerability in bwm-ng, published on 27 May 2023. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-26129 and fix it if it is affected.\n\nWhat it is: CVE-2023-26129 is a high-severity command injection vulnerability in bwm-ng, published on 27 May 2023. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-26129 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- bwm-ng (npm): affected all versions up to 0.1.1; no fix listed\n- bwm-ng (npm): affected all versions up to 0.1.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-2023-26129/ (Markdown: https://insights.sbomify.com/CVE-2023-26129/index.md)","id":"CVE-2023-26129","markdown":"https://insights.sbomify.com/CVE-2023-26129/index.md","name":"CVE-2023-26129","record":{"aliases":["GHSA-8vw3-vxmj-h43w"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"npm package","requires_auth":"none","summary":"An attacker with Node.js execution access can exploit improper input sanitization in bwm-ng to execute arbitrary commands.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"snyk","cpe":[{"product":"bwm-ng","vendor":"bwm-ng_project"}],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P","version":"3.1"},"cwes":[{"id":"CWE-77","name":"Improper Neutralization of Special Elements used in a Command"},{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"All versions of the package bwm-ng are vulnerable to Command Injection due to improper input sanitization in the 'check' function in the bwm-ng.js file. \r\r**Note:**\r\rTo execute the code snippet and potentially exploit the vulnerability, the attacker needs to have the ability to run Node.js code within the target environment. This typically requires some level of access to the system or application hosting the Node.js environment.","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":"bwm-ng vulnerable to command injection","id":"CVE-2023-26129","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"command_injection","year":"2023"},"n_packages":2,"n_references":1,"next":{"headline":"Other in yhirose/cpp-httplib","id":"CVE-2023-26130"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.1.1"],"package":"bwm-ng","purl":null,"source":"GHSA-8vw3-vxmj-h43w"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["0.1.1"],"package":"bwm-ng","purl":"pkg:npm/bwm-ng","source":"GHSA-8vw3-vxmj-h43w"}],"prev":{"headline":"keep-module-latest vulnerable to Command Injection due to missing input sanitization","id":"CVE-2023-26128"},"products":["bwm-ng"],"published":"2023-05-27","related":[{"cvss_score":7.5,"headline":"Null dereference in bwm-ng","id":"CVE-2022-1341","kev_date_added":null,"published":"2022-04-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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-01-13","vendors":["n/a"]},"summary":"An attacker with Node.js execution access can exploit improper input sanitization in bwm-ng to execute arbitrary commands.","url":"https://insights.sbomify.com/CVE-2023-26129/"}