{"answers":{"affected":"2 open source packages ship an affected version, including ggit.","exploited":"There is no known exploitation of CVE-2024-21532 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-21532 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-21532 is a high-severity command injection vulnerability in ggit, published on 8 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-21532 and fix it if it is affected.\n\nWhat it is: CVE-2024-21532 is a high-severity command injection vulnerability in ggit, published on 8 Oct 2024. 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-2024-21532 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ggit (npm): affected all versions up to 2.4.12; no fix listed\n- ggit (npm): affected all versions up to 2.4.12; 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-2024-21532/ (Markdown: https://insights.sbomify.com/CVE-2024-21532/index.md)","id":"CVE-2024-21532","markdown":"https://insights.sbomify.com/CVE-2024-21532/index.md","name":"CVE-2024-21532","record":{"aliases":["GHSA-62cx-5xj4-wfm4"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js git library","requires_auth":"none","summary":"Attackers can execute arbitrary commands via the fetchTags API in the ggit library due to unsafe string concatenation in git commands.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"snyk","cpe":[],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P","version":"3.1"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"All versions of the package ggit are vulnerable to Command Injection via the fetchTags(branch) API, which allows user input to specify the branch to be fetched and then concatenates this string along with a git command which is then passed to the unsafe exec() Node.js child process API.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":"2025-05-10","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-05-10T14:44:59Z","kind":"github_poc","ref":"https://github.com/lirantal/CVE-2024-21532-PoC-ggit","stars":0,"title":"CVE-2024-21532 PoC ggit"}],"tier":"poc_unverified"},"has_fix":false,"headline":"ggit is vulnerable to Command Injection via the fetchTags(branch) API","id":"CVE-2024-21532","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"command_injection","year":"2024"},"n_packages":2,"n_references":2,"next":{"headline":"ggit is vulnerable to Arbitrary Argument Injection via the clone() API","id":"CVE-2024-21533"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["2.4.12"],"package":"ggit","purl":null,"source":"GHSA-62cx-5xj4-wfm4"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["2.4.12"],"package":"ggit","purl":"pkg:npm/ggit","source":"GHSA-62cx-5xj4-wfm4"}],"prev":{"headline":"git-shallow-clone Argument Injection vulnerability","id":"CVE-2024-21531"},"products":["ggit"],"published":"2024-10-08","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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-21","vendors":["n/a"]},"summary":"Attackers can execute arbitrary commands via the fetchTags API in the ggit library due to unsafe string concatenation in git commands.","url":"https://insights.sbomify.com/CVE-2024-21532/"}