First published: Tue Jan 17 2023(Updated: )
A flaw was found in Git, a distributed revision control system. When parsing gitattributes, a mechanism to allow defining attributes for paths, multiple integer overflows can occur when there is a huge number of path patterns, attributes for a single pattern, or declared attribute names. 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 allow remote code execution.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/git | <0:1.8.3.1-24.el7_9 | 0:1.8.3.1-24.el7_9 |
redhat/git | <0:2.31.1-3.el8_7 | 0:2.31.1-3.el8_7 |
redhat/git | <0:2.18.4-2.el8_1 | 0:2.18.4-2.el8_1 |
redhat/git | <0:2.18.4-3.el8_2 | 0:2.18.4-3.el8_2 |
redhat/git | <0:2.27.0-3.el8_4 | 0:2.27.0-3.el8_4 |
redhat/git | <0:2.31.1-3.el8_6 | 0:2.31.1-3.el8_6 |
redhat/git | <0:2.31.1-3.el9_1 | 0:2.31.1-3.el9_1 |
redhat/git | <0:2.31.1-3.el9_0 | 0:2.31.1-3.el9_0 |
redhat/rh-git227-git | <0:2.27.0-4.el7 | 0:2.27.0-4.el7 |
Git Git-shell | <=2.30.6 | |
Git Git-shell | >=2.31.0<=2.31.5 | |
Git Git-shell | >=2.32.0<=2.32.4 | |
Git Git-shell | >=2.33.0<=2.33.5 | |
Git Git-shell | >=2.34.0<=2.34.5 | |
Git Git-shell | >=2.35.0<=2.35.5 | |
Git Git-shell | >=2.36.0<=2.36.3 | |
Git Git-shell | >=2.37.0<=2.37.4 | |
Git Git-shell | >=2.38.0<=2.38.2 | |
Git Git-shell | =2.39.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
(Appears in the following advisories)
Git is a distributed revision control system.
gitattributes are a mechanism to allow defining attributes for paths in Git repositories.
The vulnerability ID is CVE-2022-23521.
The severity of CVE-2022-23521 is critical with a CVSS score of 9.8.
To fix the vulnerability, update Git to version 2.39.0 or apply the appropriate patches provided by your vendor.