CVE-2022-23521
Assigner: GitHub_M
Published: 2023-01-17T22:17:17.765Z
State: PUBLISHED
title: gitattributes parsing integer overflow in git
problemTypes: descriptions: cweId: CWE-190
description: CWE-190: Integer Overflow or Wraparound
type: CWE
metrics: cvssV3_1: attackComplexity: LOW
attackVector: NETWORK
availabilityImpact: HIGH
baseScore: 9.8
baseSeverity: CRITICAL
confidentialityImpact: HIGH
integrityImpact: HIGH
privilegesRequired: NONE
scope: UNCHANGED
userInteraction: NONE
vectorString: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
version: 3.1
affected: vendor: git
product: git
versions: version: < 2.30.7
status: affected
version: >= 2.31.0, < 2.31.6
status: affected
version: >= 2.32.0, < 2.32.5
status: affected
version: >= 2.33.0, < 2.33.6
status: affected
version: >= 2.34.0, < 2.34.6
status: affected
version: >= 2.35.0, < 2.35.6
status: affected
version: >= 2.36.0, < 2.36.4
status: affected
version: >= 2.37.0, < 2.37.5
status: affected
version: >= 2.38.0, < 2.38.3
status: affected
version: = 2.39.0
status: affected
descriptions: value: Git is distributed revision control system. gitattributes are a mechanism to allow defining attributes for paths. These attributes can be defined by adding a `.gitattributes` file to the repository, which contains a set of file patterns and the attributes that should be set for paths matching this pattern. When parsing gitattributes, multiple integer overflows can occur when there is a huge number of path patterns, a huge number of attributes for a single pattern, or when the declared attribute names are huge. These overflows can be triggered via a crafted `.gitattributes` file that may be part of the commit history. Git silently splits lines longer than 2KB when parsing gitattributes from a file, but not when parsing them from the index. Consequentially, the failure mode depends on whether the file exists in the working tree, the index or both. This integer overflow can result in arbitrary heap reads and writes, which may result in remote code execution. The problem has been patched in the versions published on 2023-01-17, going back to v2.30.7. Users are advised to upgrade. There are no known workarounds for this issue.
source: advisory: GHSA-c738-c5qq-xg89
discovery: UNKNOWN