It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS-2023-1679 advisory.

  - 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)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

Detections

Analytics

Amazon Linux AMI : (ALAS-2023-1679)

critical Nessus Plugin ID 171055

Version 1.0