Important: git

Issue Overview:

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. (CVE-2022-23521)

Git is distributed revision control system. git log can display commits in an arbitrary format using its --format specifiers. This functionality is also exposed to git archive via the export-subst gitattribute. When processing the padding operators, there is a integer overflow in pretty.c::format_and_pad_commit() where a size_t is stored improperly as an int, and then added as an offset to a memcpy(). This overflow can be triggered directly by a user running a command which invokes the commit formatting machinery (e.g., git log --format=...). It may also be triggered indirectly through git archive via the export-subst mechanism, which expands format specifiers inside of files within the repository during a git archive. This integer overflow can result in arbitrary heap writes, which may result in arbitrary 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. Users who are unable to upgrade should disable git archive in untrusted repositories. If you expose git archive via git daemon, disable it by running git config --global daemon.uploadArch false. (CVE-2022-41903)

Affected Packages:

git

Note:

This advisory is applicable to Amazon Linux 2 (AL2) Core repository. Visit this FAQ section for the difference between AL2 Core and AL2 Extras advisories.

Issue Correction:
Run yum update git to update your system.

New Packages:

aarch64:  
    git-2.39.1-1.amzn2.0.1.aarch64  
    git-core-2.39.1-1.amzn2.0.1.aarch64  
    git-credential-libsecret-2.39.1-1.amzn2.0.1.aarch64  
    git-daemon-2.39.1-1.amzn2.0.1.aarch64  
    git-debuginfo-2.39.1-1.amzn2.0.1.aarch64  
  
i686:  
    git-2.39.1-1.amzn2.0.1.i686  
    git-core-2.39.1-1.amzn2.0.1.i686  
    git-credential-libsecret-2.39.1-1.amzn2.0.1.i686  
    git-daemon-2.39.1-1.amzn2.0.1.i686  
    git-debuginfo-2.39.1-1.amzn2.0.1.i686  
  
noarch:  
    git-all-2.39.1-1.amzn2.0.1.noarch  
    git-core-doc-2.39.1-1.amzn2.0.1.noarch  
    git-cvs-2.39.1-1.amzn2.0.1.noarch  
    git-email-2.39.1-1.amzn2.0.1.noarch  
    gitk-2.39.1-1.amzn2.0.1.noarch  
    gitweb-2.39.1-1.amzn2.0.1.noarch  
    git-gui-2.39.1-1.amzn2.0.1.noarch  
    git-instaweb-2.39.1-1.amzn2.0.1.noarch  
    git-p4-2.39.1-1.amzn2.0.1.noarch  
    perl-Git-2.39.1-1.amzn2.0.1.noarch  
    perl-Git-SVN-2.39.1-1.amzn2.0.1.noarch  
    git-subtree-2.39.1-1.amzn2.0.1.noarch  
    git-svn-2.39.1-1.amzn2.0.1.noarch  
  
src:  
    git-2.39.1-1.amzn2.0.1.src  
  
x86_64:  
    git-2.39.1-1.amzn2.0.1.x86_64  
    git-core-2.39.1-1.amzn2.0.1.x86_64  
    git-credential-libsecret-2.39.1-1.amzn2.0.1.x86_64  
    git-daemon-2.39.1-1.amzn2.0.1.x86_64  
    git-debuginfo-2.39.1-1.amzn2.0.1.x86_64  

Additional References

Red Hat: CVE-2022-23521, CVE-2022-41903

Mitre: CVE-2022-23521, CVE-2022-41903