CVE-2024-21532
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAll 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe ggit package has a command injection vulnerability in the fetchTags(branch) API. The function accepts user-supplied branch names and concatenates them directly into a git command string that is passed to Node.js's unsafe exec() function, allowing arbitrary command execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the ggit package in your projectSearch for ggit in your package.json dependencies or check for node_modules/ggit directoryAffected if The ggit package is present in your project dependencies
-
Identify the installed ggit versionRun 'npm list ggit' or check the version field in node_modules/ggit/package.jsonAffected if The installed version has not been patched for command injection (compare your version to any available patched release)
-
Find usage of fetchTags in your codebaseSearch source files for 'fetchTags' function calls using grep or IDE searchAffected if The fetchTags API is being called in your code
-
Determine if fetchTags receives user inputTrace the data flow to fetchTags(branch) calls and check if the branch parameter originates from user requests, APIs, or external sourcesAffected if User-controlled or untrusted data is passed directly to the branch parameter of fetchTags
-
Verify if input validation exists before fetchTagsSearch for sanitization, validation, or whitelist logic applied to the branch argument before it reaches fetchTagsAffected if No input validation or whitelist filtering is applied to branch names before passing to fetchTags
Your environment is affected if ggit is installed, fetchTags is used, and user-supplied branch names are passed to it without validation or sanitization.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataAvoid using this package until a patched version is available, or implement strict input validation to whitelist only safe branch name characters before passing to fetchTags(). Consider migrating to a safer alternative or using the git command directly with proper argument escaping.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-21532 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-21532 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data