Critical Memory Leak Vulnerability in Git Package

git Updated 02 Oct 2025

Summary

30/05/2018
N/A
Yes i
High
7.5

ALPINE-CVE-2018-11233: In Git before 2.13.7, 2.14.x before 2.14.4, 2.15.x before 2.15.2, 2.16.x before 2.16.4, and 2.17.x before 2.17.1, code to sanity-check pathnames on NTFS can result in reading out-of-bounds memory. Affects git versions < 2.17.1-r0. Fixed in 2.17.1-r0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

Git is a widely used version control system that allows developers to track changes in source code during software development. It is known for its speed, efficiency, and support for non-linear development workflows. However, certain versions of Git are vulnerable to a memory leak issue that can lead to unauthorized access to sensitive data on NTFS file systems.

Vulnerability Detail

The vulnerability, identified as CVE-2018-11233, affects Git versions prior to 2.13.7, 2.14.x before 2.14.4, 2.15.x before 2.15.2, 2.16.x before 2.16.4, and 2.17.x before 2.17.1. It originates from insufficient checks on pathnames when interacting with NTFS file systems, which can result in reading out-of-bounds memory. This could potentially expose sensitive information and compromise the integrity of the system, making it a significant security risk.

How To Fix

Minimum fixed version

2.17.1-r0

This is the first release that contains the fix.

sudo apk add --upgrade git

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, users can avoid using Git on NTFS file systems until the package is updated. This may involve switching to a different file system or using a virtual machine with a different operating system.

Conclusion

The CVE-2018-11233 vulnerability in Git poses a significant risk to users operating on NTFS file systems. It is crucial to update to the patched version to mitigate potential security threats. Users should remain vigilant and consider using tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for git →

Share this vulnerability

FAQ

CVE-2018-11233 is a vulnerability in Git that allows for potential memory leaks and unauthorized access to sensitive data on NTFS file systems.

Affected versions include Git versions prior to 2.13.7, 2.14.x before 2.14.4, 2.15.x before 2.15.2, 2.16.x before 2.16.4, and 2.17.x before 2.17.1.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

The CVSS score for CVE-2018-11233 is 7.5, indicating a high severity level.

If an immediate update is not possible, consider using a different file system or temporarily avoiding Git operations on NTFS until the vulnerability is patched.

Related vulnerabilities

Recent vulnerabilities recorded for git.

How To Fix

Minimum fixed version

2.17.1-r0

This is the first release that contains the fix.

sudo apk add --upgrade git

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback