dbcve.org
GitApplication · Git Scm

CVE-2022-29187

HIGH · 7.8 CVSS v3.1 Published 2022-07-12
Fix available
A fix is available. Upgrade to 2.30.5 / 2.31.4 or later.
See remediation →
80/100
Remediation priority · High
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 is a distributed revision control system. Git prior to versions 2.37.1, 2.36.2, 2.35.4, 2.34.4, 2.33.4, 2.32.3, 2.31.4, and 2.30.5, is vulnerable to privilege escalation in all platforms. An unsuspecting user could still be affected by the issue reported in CVE-2022-24765, for example when navigating as root into a shared tmp directory that is owned by them, but where an attacker could create a git repository. Versions 2.37.1, 2.36.2, 2.35.4, 2.34.4, 2.33.4, 2.32.3, 2.31.4, and 2.30.5 contain a patch for this issue. The simplest way to avoid being affected by the exploit described in the example is to avoid running git as root (or an Administrator in Windows), and if needed to reduce its use to a minimum. While a generic workaround is not possible, a system could be hardened from the exploit described in the example by removing any such repository if it exists already and creating one as root to block any future attacks.

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 versions prior to 2.37.1, 2.36.2, 2.35.4, 2.34.4, 2.33.4, 2.32.3, 2.31.4, and 2.30.5 are vulnerable to privilege escalation on all platforms. An attacker can create a malicious git repository in a shared tmp directory owned by a user; when that user (or root) navigates into that directory and runs git commands, arbitrary code can be executed with elevated privileges, bypassing protections intended for CVE-2022-24765.

MitigationUpdate Git to a patched version (2.37.1 or later, or any version listed in the fixed versions). Alternatively, avoid running git as root/Administrator, remove any attacker-created repositories in shared directories, and create a benign repository as root to block future attacks.

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
GitApplication
Affected:>= 2.30.3, < 2.30.5>= 2.31.2, < 2.31.4>= 2.32.1, < 2.32.3>= 2.33.2, < 2.33.4>= 2.34.2, < 2.34.4>= 2.35.2, < 2.35.4>= 2.36.0, < 2.36.2>= 2.37.0, < 2.37.1
FedoraOperating system
Affected:= 35= 36= 37
Debian LinuxOperating system
Affected:= 10.0
XcodeApplication
Affected:< 14.1

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 version
    Run `git --version` and compare the output to the affected version ranges: 2.30.3 to 2.30.4, 2.31.2 to 2.31.3, 2.32.1 to 2.32.2, 2.33.2 to 2.33.3, 2.34.2 to 2.34.3, 2.35.2 to 2.35.3, 2.36.0 to 2.36.1, or 2.37.0
    Affected if The installed version falls within any of the listed vulnerable ranges
  2. Identify git repositories in shared directories
    Search for .git directories in /tmp, /var/tmp, /home/*/tmp, or other shared directories. Run: `find /tmp /var/tmp -type d -name .git 2>/dev/null` and `find /home -maxdepth 3 -type d -name .git 2>/dev/null`
    Affected if Any .git repository exists in a shared or world-writable directory that you did not create
  3. Check ownership of suspicious repositories
    For each .git directory found in shared locations, run `ls -la` on the parent directory to verify if the repository owner matches your user account or if it was created by another user
    Affected if A .git directory in a shared location is owned by a different user than your current user
  4. Inspect repository hooks for malicious content
    If a suspicious repository is found, examine files in the .git/hooks directory: `ls -la .git/hooks/` and review any existing hook files for suspicious commands, especially those executing external scripts or using curl/wget with elevated privileges
    Affected if Any hook file contains commands that execute external code or run with elevated privileges when you run git commands in that directory

You are affected if your installed Git version is within the vulnerable ranges and you have navigated to or may navigate to a malicious repository in a shared directory owned by another user.

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 2.30.5 / 2.31.4 / 2.32.3 or later
Fixed in 2.30.52.31.42.32.3
Interim mitigation

Update Git to a patched version (2.37.1 or later, or any version listed in the fixed versions). Alternatively, avoid running git as root/Administrator, remove any attacker-created repositories in shared directories, and create a benign repository as root to block future attacks.

Recommended fix High confidence

Upgrade to Git 2.30.5, 2.31.4, 2.32.3, 2.33.4 or later (latest stable recommended: 2.37.1+)

  1. Check current git version by running: git --version
  2. Upgrade git to a patched version. For your current version range:
  3. - If using 2.30.x, upgrade to 2.30.5 or later
  4. - If using 2.31.x, upgrade to 2.31.4 or later
  5. - If using 2.32.x, upgrade to 2.32.3 or later
  6. - If using 2.33.x, upgrade to 2.33.4 or later
  7. On Fedora: sudo dnf update git
  8. On Debian/Ubuntu: sudo apt update && sudo apt install git
Caveat No breaking changes expected; this is a security patch release

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

Fix this in Git Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-29187 — 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-2022-29187 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