Buffer Overflow Vulnerabilities in git

git Updated 02 Oct 2025

Summary

19/03/2016
N/A
Yes i
Unrated
Not published

DSA-3521-1: git - security update. Affects git versions < 1:1.7.10.4-1+wheezy3. Fixed in 1:1.7.10.4-1+wheezy3. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Git is a fast, scalable, distributed revision control system used for tracking changes in source code during software development. It allows multiple developers to collaborate on a project efficiently. Git is widely used in the software development industry and is known for its speed and flexibility. However, two buffer overflow vulnerabilities have been discovered in git, which could potentially allow remote execution of arbitrary code.

Vulnerability Detail

The buffer overflow vulnerabilities in git arise from improper handling of certain input data. An attacker could exploit these vulnerabilities by crafting malicious input that exceeds the bounds of a buffer, leading to memory corruption. This could potentially allow the attacker to execute arbitrary code on the affected system. The impact of these vulnerabilities could be severe, as remote code execution can lead to unauthorized access, data breaches, and further compromise of the system.

How To Fix

Minimum fixed version

1:1.7.10.4-1+wheezy3

This is the first release that contains the fix.

sudo apt-get install --only-upgrade git

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

Workaround

There is no specific workaround mentioned for these vulnerabilities. The recommended action is to upgrade to the fixed versions of git.

Conclusion

The buffer overflow vulnerabilities in git can pose a significant risk to the security of systems using affected versions. It is crucial to upgrade to the fixed versions mentioned in the 'how_to_fix' section to mitigate the risk of exploitation. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for git →

Share this vulnerability

FAQ

Git is a distributed revision control system used for tracking changes in source code during software development. It allows multiple developers to collaborate on a project efficiently.

Buffer overflow vulnerabilities occur when a program writes more data into a buffer than it can handle, leading to memory corruption. This can potentially be exploited by attackers to execute arbitrary code.

These vulnerabilities can be exploited by crafting malicious input that exceeds the bounds of a buffer, causing memory corruption. This can potentially allow remote execution of arbitrary code.

The impact of these vulnerabilities can be severe. Remote code execution can lead to unauthorized access, data breaches, and further compromise of the affected system.

To fix these vulnerabilities, it is recommended to upgrade the git package to the fixed versions mentioned in the 'how_to_fix' section.

Related vulnerabilities

Recent vulnerabilities recorded for git.

How To Fix

Minimum fixed version

1:1.7.10.4-1+wheezy3

This is the first release that contains the fix.

sudo apt-get install --only-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