The version of Git for Windows installed on the remote host is affect by multiple vulnerabilities, as follows:

  - 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 this issue but has instead relied only on the application's self-reported version number.

Detections

Analytics

Git for Windows < 2.30.7 / 2.31.6 / 2.32.5 / 2.33.6 / 2.34.6 / 2.35.6 / 2.36.4 / 2.37.5 / 2.38.3 / 2.39.1 Multiple Vulnerabilities

critical Nessus Plugin ID 184470

Version 1.2

Version 1.1

Version 1.0

Version 1.2 Aug 3, 2026, 1:05 PM Detection (migrated to VDF format) Plugin Feed: 202608031305
Version 1.1 Nov 7, 2023, 3:08 PM CVSS temporal metrics ("CVSSv2 temporal vector" set to "CVSS2#E:U/RL:OF/RC:C". "CVSSv3 temporal vector" set to "CVSS:3.0/E:U/RL:O/RC:C") CVSSv2 score source (changed from "CVE-2022-23521" to "CVE-2022-41903") Exploit attributes ("Exploit available" set to "False". "Exploitability ease" set to "No known exploits are available") Plugin Feed: 202311071508
Version 1.0 Nov 6, 2023, 8:46 PM New Plugin Feed: 202311062046