cbcvebase.
CVE-2016-2324
published 2016-04-08

CVE-2016-2324: Integer overflow in Git before 2.7.4 allows remote attackers to execute arbitrary code via a (1) long filename or (2) many nested trees, which triggers a…

PriorityP264critical9.8CVSS 3.1
AVNACLPRNUINSUCHIHAH
EPSS
18.81%
97.0th percentile
Integer overflow in Git before 2.7.4 allows remote attackers to execute arbitrary code via a (1) long filename or (2) many nested trees, which triggers a heap-based buffer overflow.

Affected

17 ranges
VendorProductVersion rangeFixed in
debiancgit< git 1:2.8.0~rc3-1 (bookworm)git 1:2.8.0~rc3-1 (bookworm)
debiangit< git 1:2.8.0~rc3-1 (bookworm)git 1:2.8.0~rc3-1 (bookworm)
git-scmgit<= 2.7.3
gitgit>= 0 < 1:2.8.0~rc3-11:2.8.0~rc3-1
gitgit>= 0 < 1:2.8.0~rc3-11:2.8.0~rc3-1
gitgit>= 0 < 1:2.8.0~rc3-11:2.8.0~rc3-1
gitgit>= 0 < 1:2.8.0~rc3-11:2.8.0~rc3-1
gitgit>= 0 < 1:1.9.1-1ubuntu0.31:1.9.1-1ubuntu0.3
opensuseleap
opensuseopensuse
suselinux_enterprise_debuginfo
suselinux_enterprise_server
suselinux_enterprise_software_development_kit
suselinux_enterprise_software_development_kit
suselinux_enterprise_software_development_kit
suseopenstack_cloud
susesuse_linux_enterprise_server

Detection & IOCsextracted from sources · hover to see the quote

  • The vulnerability exists in the `path_name()` function in `revision.c`. Monitor for exploitation attempts targeting this function via crafted packfiles with excessively long filenames or deeply nested tree structures.
  • CVE-2016-2324 is triggered by an integer overflow in the loop that accumulates path element lengths into `len`. Detect by monitoring Git operations (clone/push/fetch) involving repositories with a very large number of nested trees or extremely long filenames that could overflow a signed `int`.
  • Attack vector is a specially crafted packfile delivered via push (attacker needs push access) or clone (user tricked into cloning malicious repo). Alert on unexpected Git process crashes (heap corruption) during clone/fetch/push operations as a potential exploitation indicator.
  • For server-side exposure, the attacker must be authenticated and able to push to a repository. Audit push access controls and monitor server-side Git crashes during pack reception on versions prior to 2.4.11, 2.5.5, 2.6.6, or 2.7.4.
  • For client-side exposure, monitor for users cloning from untrusted or unknown Git repositories. A crash of the git process during clone is a strong indicator of exploitation attempt.
  • ·The vulnerability affects Git versions before 2.7.4 (also fixed in backport releases 2.4.11, 2.5.5, and 2.6.6). Ensure all Git installations are at or above these versions.
  • ·Exploitation results in heap corruption that most likely crashes Git, but arbitrary code execution cannot be ruled out. Treat any unexplained Git crash during pack processing as a potential security event.
  • ·The original vulnerability report and PoC details are referenced at http://pastebin.com/UX2P2jjg and http://seclists.org/oss-sec/2016/q1/645 — review these for additional technical context on crafted repository structure.

CVSS provenance

nvdv3.19.8CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvdv2.010.0CRITICALAV:N/AC:L/Au:N/C:C/I:C/A:C
osv9.8CRITICAL
vendor_debian9.8LOW
vendor_redhat9.8CRITICAL
vendor_ubuntu9.8CRITICAL
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.