dbcve.org
GitApplication · Git Scm

CVE-2023-23946

HIGH · 7.5 CVSS v3.1 Published 2023-02-14
Fix available
A fix is available. Upgrade to 2.30.8 / 2.31.7 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click Patch available

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, a revision control system, is vulnerable to path traversal prior to versions 2.39.2, 2.38.4, 2.37.6, 2.36.5, 2.35.7, 2.34.7, 2.33.7, 2.32.6, 2.31.7, and 2.30.8. By feeding a crafted input to `git apply`, a path outside the working tree can be overwritten as the user who is running `git apply`. A fix has been prepared and will appear in v2.39.2, v2.38.4, v2.37.6, v2.36.5, v2.35.7, v2.34.7, v2.33.7, v2.32.6, v2.31.7, and v2.30.8. As a workaround, use `git apply --stat` to inspect a patch before applying; avoid applying one that creates a symbolic link and then creates a file beyond the symbolic link.

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
How this class of weakness works · CWE-22

A file path is built from user input without being confined, so sequences like “../” let an attacker step outside the intended directory. That can expose configuration, credentials, or source code, and in the worst case lets an attacker write files where they shouldn't. A durable fix resolves and canonicalises the path, then rejects anything that escapes a known-safe base directory.

General guidance for the path traversal class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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.8>= 2.31.0, < 2.31.7>= 2.32.0, < 2.32.6>= 2.33.0, < 2.33.7>= 2.34.0, < 2.34.7>= 2.35.0, < 2.35.7>= 2.36.0, < 2.36.5>= 2.37.0, < 2.37.6>= 2.38.0, < 2.38.4>= 2.39.0, < 2.39.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
None
Integrity
High
Availability
None

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

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.8 / 2.31.7 / 2.32.6 or later
Fixed in 2.30.82.31.72.32.6
Vendor patch github.com →
Recommended fix High confidence

Upgrade to git >= 2.30.8, 2.31.7, 2.32.6, or 2.33.7 (depending on your current version branch); recommended: 2.39.2 or later for the most recent stable release with all fixes

  1. 1. Identify the current git version by running: git --version
  2. 2. Determine which upgrade path applies based on your current version (see upgrade_path)
  3. 3. For Debian/Ubuntu: Run 'sudo apt-get update && sudo apt-get install git' to get the latest available version in your distribution's repositories
  4. 4. For RHEL/CentOS: Run 'sudo yum update git' or 'sudo dnf update git'
  5. 5. For macOS with Homebrew: Run 'brew upgrade git'
  6. 6. For Windows: Download and install the latest version from https://git-scm.com/download/win
  7. 7. Alternatively, build from source using the commit c867e4fa180bec4750e9b54eb10f459030dbebfd or a later tagged release
  8. 8. Verify the fix by checking: git --version (should show >= 2.30.8, 2.31.7, 2.32.6, or 2.33.7 depending on your version line)
Caveat Minor: Git version upgrades rarely introduce breaking changes for normal workflows; however, verify compatibility with any custom hooks or scripts

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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