# CVE-2024-21533: ggit is vulnerable to Arbitrary Argument Injection via the clone() API

> Attackers can execute arbitrary commands via the clone() API due to lack of input sanitization and proper flag handling in the ggit library.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Oct 2024
- **Updated:** 21 Mar 2026
- **Also known as:** GHSA-pr45-cg4x-ff4m

## What is CVE-2024-21533?

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.

### Official 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.

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command)

## Which versions are affected by CVE-2024-21533?

2 open source packages ship an affected version, including ggit.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ggit` | npm | All versions to 2.4.12 | None |
| `ggit` | npm | All versions to 2.4.12 | None |

## How do I fix CVE-2024-21533?

No fix has been published for CVE-2024-21533 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-21533 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-21533 exists.

Public exploit code:

- CVE-2024-21533 PoC ggit (github_poc): https://github.com/lirantal/CVE-2024-21533-PoC-ggit

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-21533 and fix it if it is affected.

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-21533 exists.

Affected packages and fixed versions:
- ggit (npm): affected all versions up to 2.4.12; no fix listed
- ggit (npm): affected all versions up to 2.4.12; no fix listed

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-21533/ (Markdown: https://insights.sbomify.com/CVE-2024-21533/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-21533
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-21533
- OSV: https://osv.dev/vulnerability/CVE-2024-21533

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-21533/
Summaries are generated and may contain mistakes; the official description above is the record.