dbcve.org
GitApplication · Git Scm

CVE-2019-1353

CRITICAL · 9.8 CVSS v3.1 Published 2020-01-24
Fix available
A fix is available. Upgrade to 2.14.6 / 2.15.4 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
An issue was found in Git before v2.24.1, v2.23.1, v2.22.2, v2.21.1, v2.20.2, v2.19.3, v2.18.2, v2.17.3, v2.16.6, v2.15.4, and v2.14.6. When running Git in the Windows Subsystem for Linux (also known as "WSL") while accessing a working directory on a regular Windows drive, none of the NTFS protections were active.

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

When Git runs in Windows Subsystem for Linux (WSL) and accesses a working directory on a regular Windows drive (e.g., /mnt/c/), the NTFS filesystem protections are bypassed. These protections normally guard against NTFS alternate data streams (ADS) abuse, case-insensitive filename collisions, and other Windows-specific attack vectors involving maliciously crafted filenames.

MitigationUpgrade Git to v2.24.1, v2.23.1, v2.22.2, v2.21.1, v2.20.2, v2.19.3, v2.18.2, v2.17.3, v2.16.6, v2.15.4, or v2.14.6 or later on WSL environments that access Windows drives.

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.14.0, < 2.14.6>= 2.15.0, < 2.15.4>= 2.16.0, < 2.16.6>= 2.17.0, < 2.17.3>= 2.18.0, < 2.18.2>= 2.19.0, < 2.19.3>= 2.20.0, < 2.20.2>= 2.21.0, < 2.21.1>= 2.22.0, < 2.22.2>= 2.23.0, < 2.23.1>= 2.24.0, < 2.24.1
LeapOperating system
Affected:= 15.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
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. Confirm WSL environment
    Check /proc/version or run 'uname -a' and look for 'Microsoft' or 'WSL' in the output
    Affected if The environment is running inside Windows Subsystem for Linux
  2. Check installed Git version
    Run 'git --version' and compare the output to the affected ranges: 2.14.0 to 2.14.5, 2.15.0 to 2.15.3, 2.16.0 to 2.16.5, 2.17.0 to 2.17.2, 2.18.0 to 2.18.1, 2.19.0 to 2.19.2, 2.20.0 to 2.20.1, 2.21.0, 2.22.0 to 2.22.1, 2.23.0, 2.24.0
    Affected if The installed Git version falls within any of the listed vulnerable ranges
  3. Identify WSL drive mounts
    List contents of /mnt/ directory or run 'mount | grep /mnt' to see if Windows drives are mounted
    Affected if Windows drives (such as /mnt/c/) are mounted and accessible from WSL
  4. Check for Git repositories on Windows drives
    Run 'git rev-parse --show-toplevel' inside any repository located under /mnt/ or similar Windows mount points
    Affected if A Git repository is located on a Windows drive accessed through WSL mount points

A user is affected if they are running a vulnerable Git version inside WSL and working with repositories stored on Windows drives mounted under /mnt/.

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.14.6 / 2.15.4 / 2.16.6 or later
Fixed in 2.14.62.15.42.16.6
Interim mitigation

Upgrade Git to v2.24.1, v2.23.1, v2.22.2, v2.21.1, v2.20.2, v2.19.3, v2.18.2, v2.17.3, v2.16.6, v2.15.4, or v2.14.6 or later on WSL environments that access Windows drives.

Recommended fix High confidence

Upgrade to Git v2.24.1 or later (or at minimum: v2.14.6, v2.15.4, v2.16.6, or v2.17.3 depending on your release line)

  1. Check current Git version by running: git --version
  2. For Debian/Ubuntu-based systems: sudo apt-get update && sudo apt-get install git
  3. For RHEL/CentOS/Fedora: sudo yum update git or sudo dnf update git
  4. For SUSE-based systems (including Leap): sudo zypper update git
  5. For Windows WSL: Upgrade through your distribution's package manager as above, or download from https://git-scm.com/
  6. Verify the upgrade was successful by running: git --version
Caveat Git minor version upgrades rarely introduce breaking changes for typical usage; however, review release notes for your target version if you rely on specific Git behaviors

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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