{"answers":{"affected":"2 open source packages ship an affected version, including git-commit-info. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-26134 exists.","fix":"Upgrade git-commit-info to 2.0.2 or later.","what":"CVE-2023-26134 is a critical command injection vulnerability in git-commit-info, published on 28 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-26134 and fix it if it is affected.\n\nWhat it is: CVE-2023-26134 is a critical command injection vulnerability in git-commit-info, published on 28 Jun 2023. 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-2023-26134 exists.\n\nAffected packages and fixed versions:\n- git-commit-info (npm): affected all versions; fixed in 2.0.2\n- git-commit-info (npm): affected all versions; fixed in 2.0.2\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-26134/ (Markdown: https://insights.sbomify.com/CVE-2023-26134/index.md)","id":"CVE-2023-26134","markdown":"https://insights.sbomify.com/CVE-2023-26134/index.md","name":"CVE-2023-26134","record":{"aliases":["GHSA-h42j-mrmp-9369"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"npm git-commit-info library","requires_auth":"none","summary":"Attackers can execute arbitrary commands by injecting malicious content into the commit hash parameter of the git-commit-info library.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"snyk","cpe":[{"product":"git-commit-info","vendor":"git-commit-info_project"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/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":"Versions of the package git-commit-info before 2.0.2 are vulnerable to Command Injection such that the package-exported method gitCommitInfo () fails to sanitize its parameter commit, which later flows into a sensitive command execution API. As a result, attackers may inject malicious commands once they control the hash content.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"git-commit-info vulnerable to Command Injection","id":"CVE-2023-26134","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"command_injection","year":"2023"},"n_packages":2,"n_references":3,"next":{"headline":"flatnest Prototype Pollution vulnerability","id":"CVE-2023-26135"},"packages":[{"ecosystem":"npm","fixed":["2.0.2"],"introduced":["0"],"last_affected":[],"package":"git-commit-info","purl":null,"source":"GHSA-h42j-mrmp-9369"},{"ecosystem":"npm","fixed":["2.0.2"],"introduced":["0"],"last_affected":[],"package":"git-commit-info","purl":"pkg:npm/git-commit-info","source":"GHSA-h42j-mrmp-9369"}],"prev":{"headline":"progressbar.js vulnerable to Prototype Pollution","id":"CVE-2023-26133"},"products":["git-commit-info"],"published":"2023-06-28","related":[],"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":"2024-11-27","vendors":["n/a"]},"summary":"Attackers can execute arbitrary commands by injecting malicious content into the commit hash parameter of the git-commit-info library.","url":"https://insights.sbomify.com/CVE-2023-26134/"}