{"answers":{"affected":"2 open source packages ship an affected version, including ggit.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-21533 exists.","fix":"No fix has been published for CVE-2024-21533 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-21533 is a medium-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-21533 and fix it if it is affected.\n\nWhat it is: CVE-2024-21533 is a medium-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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-21533 exists.\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-21533/ (Markdown: https://insights.sbomify.com/CVE-2024-21533/index.md)","id":"CVE-2024-21533","markdown":"https://insights.sbomify.com/CVE-2024-21533/index.md","name":"CVE-2024-21533","record":{"aliases":["GHSA-pr45-cg4x-ff4m"],"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 clone() API due to lack of input sanitization and proper flag handling in the ggit library.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"snyk","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L/E:P","version":"3.1"},"cwes":[{"id":"CWE-88","name":"Improper Neutralization of Argument Delimiters in a Command"}],"description":"All versions of the package ggit are vulnerable to Arbitrary Argument Injection via the clone() API, which allows specifying the remote URL to clone and the file on disk to clone to. The library does not sanitize for user input or validate a given URL scheme, nor does it properly pass command-line flags to the git binary using the double-dash POSIX characters (--) to communicate the end of options.","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:46:58Z","kind":"github_poc","ref":"https://github.com/lirantal/CVE-2024-21533-PoC-ggit","stars":0,"title":"CVE-2024-21533 PoC ggit"}],"tier":"weaponised"},"has_fix":false,"headline":"ggit is vulnerable to Arbitrary Argument Injection via the clone() API","id":"CVE-2024-21533","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":"JSONPath Plus Remote Code Execution (RCE) Vulnerability","id":"CVE-2024-21534"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["2.4.12"],"package":"ggit","purl":null,"source":"GHSA-pr45-cg4x-ff4m"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["2.4.12"],"package":"ggit","purl":"pkg:npm/ggit","source":"GHSA-pr45-cg4x-ff4m"}],"prev":{"headline":"ggit is vulnerable to Command Injection via the fetchTags(branch) API","id":"CVE-2024-21532"},"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-21","vendors":["n/a"]},"summary":"Attackers can execute arbitrary commands via the clone() API due to lack of input sanitization and proper flag handling in the ggit library.","url":"https://insights.sbomify.com/CVE-2024-21533/"}