dbcve.org
Git BugApplication · Git Bug Project

CVE-2021-28955

CRITICAL · 9.8 CVSS v3.1 Published 2021-03-22
Fix available
A fix is available. Upgrade to 0.7.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
git-bug before 0.7.2 has an Uncontrolled Search Path Element. It will execute git.bat from the current directory in certain PATH situations (most often seen on Windows).

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 confidence

git-bug before version 0.7.2 contains an uncontrolled search path element vulnerability where the application will execute a malicious git.bat file from the current working directory instead of the legitimate system PATH git executable. This search path hijacking allows local privilege escalation or code execution when an attacker places a crafted git.bat in a directory from which the victim runs git-bug.

MitigationUpgrade git-bug to version 0.7.2 or later which includes the fix for this vulnerability. Additionally, avoid running git-bug from untrusted or shared directories and ensure the current working directory is not writable by untrusted users.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Git BugApplication
Affected:< 0.7.2

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed git-bug version
    Run 'git-bug version' or 'git-bug --version' to determine the installed version
    Affected if The version shown is less than 0.7.2 (for example, 0.7.1, 0.7.0, or any version before 0.7.2)
  2. Inspect current working directory for git.bat
    Before running git-bug, list the contents of the current directory and check if a file named 'git.bat' exists using 'dir' on Windows or 'ls' on Unix-like systems
    Affected if A file named 'git.bat' exists in the directory from which git-bug will be executed
  3. Verify git-bug does not use absolute path for git invocation
    Examine how git-bug invokes git by reviewing source code or running git-bug with debugging/tracing enabled to see if it calls 'git' without an absolute path
    Affected if git-bug invokes git using only the command name 'git' without resolving to an absolute path from PATH, allowing current directory lookup to take precedence
  4. Check current directory write permissions
    Review file system permissions on directories where you typically run git-bug to determine if untrusted users can write files there
    Affected if The current working directory or any directory in the execution path is writable by untrusted or unprivileged users

You are affected if git-bug version is less than 0.7.2 AND a malicious git.bat file could be placed in or already exists in the current working directory where git-bug is executed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 0.7.2 or later
Fixed in 0.7.2
Interim mitigation

Upgrade git-bug to version 0.7.2 or later which includes the fix for this vulnerability. Additionally, avoid running git-bug from untrusted or shared directories and ensure the current working directory is not writable by untrusted users.

Recommended fix Moderate confidence

0.7.2

  1. 1. Check current git-bug version by running: git-bug version
  2. 2. If version is below 0.7.2, upgrade to version 0.7.2 or later
  3. 3. On Windows specifically, ensure git is in your system PATH with a fully qualified path rather than relying on current directory execution
  4. 4. After upgrading, verify the fix by checking that git-bug now uses fully qualified paths for git execution

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Git Bug Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-28955 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-28955 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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