The remote AlmaLinux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the ALSA-2023:2319 advisory.

  - Git for Windows is a fork of Git containing Windows-specific patches. This vulnerability affects users     working on multi-user machines, where untrusted parties have write access to the same hard disk. Those     untrusted parties could create the folder `C:\.git`, which would be picked up by Git operations run     supposedly outside a repository while searching for a Git directory. Git would then respect any config in     said Git directory. Git Bash users who set `GIT_PS1_SHOWDIRTYSTATE` are vulnerable as well. Users who     installed posh-gitare vulnerable simply by starting a PowerShell. Users of IDEs such as Visual Studio are     vulnerable: simply creating a new project would already read and respect the config specified in     `C:\.git\config`. Users of the Microsoft fork of Git are vulnerable simply by starting a Git Bash. The     problem has been patched in Git for Windows v2.35.2. Users unable to upgrade may create the folder `.git`     on all drives where Git commands are run, and remove read/write access from those folders as a workaround.
    Alternatively, define or extend `GIT_CEILING_DIRECTORIES` to cover the _parent_ directory of the user     profile, e.g. `C:\Users` if the user profile is located in `C:\Users\my-user-name`. (CVE-2022-24765)

  - Git is a distributed revision control system. Git prior to versions 2.37.1, 2.36.2, 2.35.4, 2.34.4,     2.33.4, 2.32.3, 2.31.4, and 2.30.5, is vulnerable to privilege escalation in all platforms. An     unsuspecting user could still be affected by the issue reported in CVE-2022-24765, for example when     navigating as root into a shared tmp directory that is owned by them, but where an attacker could create a     git repository. Versions 2.37.1, 2.36.2, 2.35.4, 2.34.4, 2.33.4, 2.32.3, 2.31.4, and 2.30.5 contain a     patch for this issue. The simplest way to avoid being affected by the exploit described in the example is     to avoid running git as root (or an Administrator in Windows), and if needed to reduce its use to a     minimum. While a generic workaround is not possible, a system could be hardened from the exploit described     in the example by removing any such repository if it exists already and creating one as root to block any     future attacks. (CVE-2022-29187)

  - Git is an open source, scalable, distributed revision control system. Versions prior to 2.30.6, 2.31.5,     2.32.4, 2.33.5, 2.34.5, 2.35.5, 2.36.3, and 2.37.4 are subject to exposure of sensitive information to a     malicious actor. When performing a local clone (where the source and target of the clone are on the same     volume), Git copies the contents of the source's `$GIT_DIR/objects` directory into the destination by     either creating hardlinks to the source contents, or copying them (if hardlinks are disabled via `--no-     hardlinks`). A malicious actor could convince a victim to clone a repository with a symbolic link pointing     at sensitive information on the victim's machine. This can be done either by having the victim clone a     malicious repository on the same machine, or having them clone a malicious repository embedded as a bare     repository via a submodule from any source, provided they clone with the `--recurse-submodules` option.
    Git does not create symbolic links in the `$GIT_DIR/objects` directory. The problem has been patched in     the versions published on 2022-10-18, and backported to v2.30.x. Potential workarounds: Avoid cloning     untrusted repositories using the `--local` optimization when on a shared machine, either by passing the     `--no-local` option to `git clone` or cloning from a URL that uses the `file://` scheme. Alternatively,     avoid cloning repositories from untrusted sources with `--recurse-submodules` or run `git config --global     protocol.file.allow user`. (CVE-2022-39253)

  - Git is an open source, scalable, distributed revision control system. `git shell` is a restricted login     shell that can be used to implement Git's push/pull functionality via SSH. In versions prior to 2.30.6,     2.31.5, 2.32.4, 2.33.5, 2.34.5, 2.35.5, 2.36.3, and 2.37.4, the function that splits the command arguments     into an array improperly uses an `int` to represent the number of entries in the array, allowing a     malicious actor to intentionally overflow the return value, leading to arbitrary heap writes. Because the     resulting array is then passed to `execv()`, it is possible to leverage this attack to gain remote code     execution on a victim machine. Note that a victim must first allow access to `git shell` as a login shell     in order to be vulnerable to this attack. This problem is patched in versions 2.30.6, 2.31.5, 2.32.4,     2.33.5, 2.34.5, 2.35.5, 2.36.3, and 2.37.4 and users are advised to upgrade to the latest version.
    Disabling `git shell` access via remote logins is a viable short-term workaround. (CVE-2022-39260)

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

The remote AlmaLinux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the ALSA-2023:2859 advisory.

  - Git for Windows is a fork of Git containing Windows-specific patches. This vulnerability affects users     working on multi-user machines, where untrusted parties have write access to the same hard disk. Those     untrusted parties could create the folder `C:\.git`, which would be picked up by Git operations run     supposedly outside a repository while searching for a Git directory. Git would then respect any config in     said Git directory. Git Bash users who set `GIT_PS1_SHOWDIRTYSTATE` are vulnerable as well. Users who     installed posh-gitare vulnerable simply by starting a PowerShell. Users of IDEs such as Visual Studio are     vulnerable: simply creating a new project would already read and respect the config specified in     `C:\.git\config`. Users of the Microsoft fork of Git are vulnerable simply by starting a Git Bash. The     problem has been patched in Git for Windows v2.35.2. Users unable to upgrade may create the folder `.git`     on all drives where Git commands are run, and remove read/write access from those folders as a workaround.
    Alternatively, define or extend `GIT_CEILING_DIRECTORIES` to cover the _parent_ directory of the user     profile, e.g. `C:\Users` if the user profile is located in `C:\Users\my-user-name`. (CVE-2022-24765)

  - Git is a distributed revision control system. Git prior to versions 2.37.1, 2.36.2, 2.35.4, 2.34.4,     2.33.4, 2.32.3, 2.31.4, and 2.30.5, is vulnerable to privilege escalation in all platforms. An     unsuspecting user could still be affected by the issue reported in CVE-2022-24765, for example when     navigating as root into a shared tmp directory that is owned by them, but where an attacker could create a     git repository. Versions 2.37.1, 2.36.2, 2.35.4, 2.34.4, 2.33.4, 2.32.3, 2.31.4, and 2.30.5 contain a     patch for this issue. The simplest way to avoid being affected by the exploit described in the example is     to avoid running git as root (or an Administrator in Windows), and if needed to reduce its use to a     minimum. While a generic workaround is not possible, a system could be hardened from the exploit described     in the example by removing any such repository if it exists already and creating one as root to block any     future attacks. (CVE-2022-29187)

  - Git is an open source, scalable, distributed revision control system. Versions prior to 2.30.6, 2.31.5,     2.32.4, 2.33.5, 2.34.5, 2.35.5, 2.36.3, and 2.37.4 are subject to exposure of sensitive information to a     malicious actor. When performing a local clone (where the source and target of the clone are on the same     volume), Git copies the contents of the source's `$GIT_DIR/objects` directory into the destination by     either creating hardlinks to the source contents, or copying them (if hardlinks are disabled via `--no-     hardlinks`). A malicious actor could convince a victim to clone a repository with a symbolic link pointing     at sensitive information on the victim's machine. This can be done either by having the victim clone a     malicious repository on the same machine, or having them clone a malicious repository embedded as a bare     repository via a submodule from any source, provided they clone with the `--recurse-submodules` option.
    Git does not create symbolic links in the `$GIT_DIR/objects` directory. The problem has been patched in     the versions published on 2022-10-18, and backported to v2.30.x. Potential workarounds: Avoid cloning     untrusted repositories using the `--local` optimization when on a shared machine, either by passing the     `--no-local` option to `git clone` or cloning from a URL that uses the `file://` scheme. Alternatively,     avoid cloning repositories from untrusted sources with `--recurse-submodules` or run `git config --global     protocol.file.allow user`. (CVE-2022-39253)

  - Git is an open source, scalable, distributed revision control system. `git shell` is a restricted login     shell that can be used to implement Git's push/pull functionality via SSH. In versions prior to 2.30.6,     2.31.5, 2.32.4, 2.33.5, 2.34.5, 2.35.5, 2.36.3, and 2.37.4, the function that splits the command arguments     into an array improperly uses an `int` to represent the number of entries in the array, allowing a     malicious actor to intentionally overflow the return value, leading to arbitrary heap writes. Because the     resulting array is then passed to `execv()`, it is possible to leverage this attack to gain remote code     execution on a victim machine. Note that a victim must first allow access to `git shell` as a login shell     in order to be vulnerable to this attack. This problem is patched in versions 2.30.6, 2.31.5, 2.32.4,     2.33.5, 2.34.5, 2.35.5, 2.36.3, and 2.37.4 and users are advised to upgrade to the latest version.
    Disabling `git shell` access via remote logins is a viable short-term workaround. (CVE-2022-39260)

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

According to the versions of the git packages installed, the EulerOS Virtualization installation on the remote host is affected by the following vulnerabilities :

  - 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 a distributed revision control system. Git prior to versions 2.37.1, 2.36.2, 2.35.4, 2.34.4,     2.33.4, 2.32.3, 2.31.4, and 2.30.5, is vulnerable to privilege escalation in all platforms. An     unsuspecting user could still be affected by the issue reported in CVE-2022-24765, for example when     navigating as root into a shared tmp directory that is owned by them, but where an attacker could create a     git repository. Versions 2.37.1, 2.36.2, 2.35.4, 2.34.4, 2.33.4, 2.32.3, 2.31.4, and 2.30.5 contain a     patch for this issue. The simplest way to avoid being affected by the exploit described in the example is     to avoid running git as root (or an Administrator in Windows), and if needed to reduce its use to a     minimum. While a generic workaround is not possible, a system could be hardened from the exploit described     in the example by removing any such repository if it exists already and creating one as root to block any     future attacks. (CVE-2022-29187)

  - Git is an open source, scalable, distributed revision control system. `git shell` is a restricted login     shell that can be used to implement Git's push/pull functionality via SSH. In versions prior to 2.30.6,     2.31.5, 2.32.4, 2.33.5, 2.34.5, 2.35.5, 2.36.3, and 2.37.4, the function that splits the command arguments     into an array improperly uses an `int` to represent the number of entries in the array, allowing a     malicious actor to intentionally overflow the return value, leading to arbitrary heap writes. Because the     resulting array is then passed to `execv()`, it is possible to leverage this attack to gain remote code     execution on a victim machine. Note that a victim must first allow access to `git shell` as a login shell     in order to be vulnerable to this attack. This problem is patched in versions 2.30.6, 2.31.5, 2.32.4,     2.33.5, 2.34.5, 2.35.5, 2.36.3, and 2.37.4 and users are advised to upgrade to the latest version.
    Disabling `git shell` access via remote logins is a viable short-term workaround. (CVE-2022-39260)

  - 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 Tenable Network Security has extracted the preceding description block directly from the EulerOS security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The remote host is affected by the vulnerability described in GLSA-202312-15 (Git: Multiple Vulnerabilities)

  - 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 for Windows is a fork of Git containing Windows-specific patches. This vulnerability affects users     working on multi-user machines, where untrusted parties have write access to the same hard disk. Those     untrusted parties could create the folder `C:\.git`, which would be picked up by Git operations run     supposedly outside a repository while searching for a Git directory. Git would then respect any config in     said Git directory. Git Bash users who set `GIT_PS1_SHOWDIRTYSTATE` are vulnerable as well. Users who     installed posh-gitare vulnerable simply by starting a PowerShell. Users of IDEs such as Visual Studio are     vulnerable: simply creating a new project would already read and respect the config specified in     `C:\.git\config`. Users of the Microsoft fork of Git are vulnerable simply by starting a Git Bash. The     problem has been patched in Git for Windows v2.35.2. Users unable to upgrade may create the folder `.git`     on all drives where Git commands are run, and remove read/write access from those folders as a workaround.
    Alternatively, define or extend `GIT_CEILING_DIRECTORIES` to cover the _parent_ directory of the user     profile, e.g. `C:\Users` if the user profile is located in `C:\Users\my-user-name`. (CVE-2022-24765)

  - Git is a distributed revision control system. Git prior to versions 2.37.1, 2.36.2, 2.35.4, 2.34.4,     2.33.4, 2.32.3, 2.31.4, and 2.30.5, is vulnerable to privilege escalation in all platforms. An     unsuspecting user could still be affected by the issue reported in CVE-2022-24765, for example when     navigating as root into a shared tmp directory that is owned by them, but where an attacker could create a     git repository. Versions 2.37.1, 2.36.2, 2.35.4, 2.34.4, 2.33.4, 2.32.3, 2.31.4, and 2.30.5 contain a     patch for this issue. The simplest way to avoid being affected by the exploit described in the example is     to avoid running git as root (or an Administrator in Windows), and if needed to reduce its use to a     minimum. While a generic workaround is not possible, a system could be hardened from the exploit described     in the example by removing any such repository if it exists already and creating one as root to block any     future attacks. (CVE-2022-29187)

  - Git is an open source, scalable, distributed revision control system. Versions prior to 2.30.6, 2.31.5,     2.32.4, 2.33.5, 2.34.5, 2.35.5, 2.36.3, and 2.37.4 are subject to exposure of sensitive information to a     malicious actor. When performing a local clone (where the source and target of the clone are on the same     volume), Git copies the contents of the source's `$GIT_DIR/objects` directory into the destination by     either creating hardlinks to the source contents, or copying them (if hardlinks are disabled via `--no-     hardlinks`). A malicious actor could convince a victim to clone a repository with a symbolic link pointing     at sensitive information on the victim's machine. This can be done either by having the victim clone a     malicious repository on the same machine, or having them clone a malicious repository embedded as a bare     repository via a submodule from any source, provided they clone with the `--recurse-submodules` option.
    Git does not create symbolic links in the `$GIT_DIR/objects` directory. The problem has been patched in     the versions published on 2022-10-18, and backported to v2.30.x. Potential workarounds: Avoid cloning     untrusted repositories using the `--local` optimization when on a shared machine, either by passing the     `--no-local` option to `git clone` or cloning from a URL that uses the `file://` scheme. Alternatively,     avoid cloning repositories from untrusted sources with `--recurse-submodules` or run `git config --global     protocol.file.allow user`. (CVE-2022-39253)

  - Git is an open source, scalable, distributed revision control system. `git shell` is a restricted login     shell that can be used to implement Git's push/pull functionality via SSH. In versions prior to 2.30.6,     2.31.5, 2.32.4, 2.33.5, 2.34.5, 2.35.5, 2.36.3, and 2.37.4, the function that splits the command arguments     into an array improperly uses an `int` to represent the number of entries in the array, allowing a     malicious actor to intentionally overflow the return value, leading to arbitrary heap writes. Because the     resulting array is then passed to `execv()`, it is possible to leverage this attack to gain remote code     execution on a victim machine. Note that a victim must first allow access to `git shell` as a login shell     in order to be vulnerable to this attack. This problem is patched in versions 2.30.6, 2.31.5, 2.32.4,     2.33.5, 2.34.5, 2.35.5, 2.36.3, and 2.37.4 and users are advised to upgrade to the latest version.
    Disabling `git shell` access via remote logins is a viable short-term workaround. (CVE-2022-39260)

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

  - Git is a revision control system. Using a specially-crafted repository, Git prior to versions 2.39.2,     2.38.4, 2.37.6, 2.36.5, 2.35.7, 2.34.7, 2.33.7, 2.32.6, 2.31.7, and 2.30.8 can be tricked into using its     local clone optimization even when using a non-local transport. Though Git will abort local clones whose     source `$GIT_DIR/objects` directory contains symbolic links, the `objects` directory itself may still be a     symbolic link. These two may be combined to include arbitrary files based on known paths on the victim's     filesystem within the malicious repository's working copy, allowing for data exfiltration in a similar     manner as CVE-2022-39253. A fix has been prepared and will appear in v2.39.2 v2.38.4 v2.37.6 v2.36.5     v2.35.7 v2.34.7 v2.33.7 v2.32.6, v2.31.7 and v2.30.8. If upgrading is impractical, two short-term     workarounds are available. Avoid cloning repositories from untrusted sources with `--recurse-submodules`.
    Instead, consider cloning repositories without recursively cloning their submodules, and instead run `git     submodule update` at each layer. Before doing so, inspect each new `.gitmodules` file to ensure that it     does not contain suspicious module URLs. (CVE-2023-22490)

  - Git, a revision control system, is vulnerable to path traversal prior to versions 2.39.2, 2.38.4, 2.37.6,     2.36.5, 2.35.7, 2.34.7, 2.33.7, 2.32.6, 2.31.7, and 2.30.8. By feeding a crafted input to `git apply`, a     path outside the working tree can be overwritten as the user who is running `git apply`. A fix has been     prepared and will appear in v2.39.2, v2.38.4, v2.37.6, v2.36.5, v2.35.7, v2.34.7, v2.33.7, v2.32.6,     v2.31.7, and v2.30.8. As a workaround, use `git apply --stat` to inspect a patch before applying; avoid     applying one that creates a symbolic link and then creates a file beyond the symbolic link.
    (CVE-2023-23946)

  - Git is a revision control system. Prior to versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8,     2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1, by feeding specially crafted input to `git apply --reject`, a     path outside the working tree can be overwritten with partially controlled contents (corresponding to the     rejected hunk(s) from the given patch). A fix is available in versions 2.30.9, 2.31.8, 2.32.7, 2.33.8,     2.34.8, 2.35.8, 2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1. As a workaround, avoid using `git apply` with     `--reject` when applying patches from an untrusted source. Use `git apply --stat` to inspect a patch     before applying; avoid applying one that create a conflict where a link corresponding to the `*.rej` file     exists. (CVE-2023-25652)

  - In Git for Windows, the Windows port of Git, no localized messages are shipped with the installer. As a     consequence, Git is expected not to localize messages at all, and skips the gettext initialization.
    However, due to a change in MINGW-packages, the `gettext()` function's implicit initialization no longer     uses the runtime prefix but uses the hard-coded path `C:\mingw64\share\locale` to look for localized     messages. And since any authenticated user has the permission to create folders in `C:\` (and since     `C:\mingw64` does not typically exist), it is possible for low-privilege users to place fake messages in     that location where `git.exe` will pick them up in version 2.40.1. This vulnerability is relatively hard     to exploit and requires social engineering. For example, a legitimate message at the end of a clone could     be maliciously modified to ask the user to direct their web browser to a malicious website, and the user     might think that the message comes from Git and is legitimate. It does require local write access by the     attacker, though, which makes this attack vector less likely. Version 2.40.1 contains a patch for this     issue. Some workarounds are available. Do not work on a Windows machine with shared accounts, or     alternatively create a `C:\mingw64` folder and leave it empty. Users who have administrative rights may     remove the permission to create folders in `C:\`. (CVE-2023-25815)

  - Git is a revision control system. Prior to versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8,     2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1, a specially crafted `.gitmodules` file with submodule URLs     that are longer than 1024 characters can used to exploit a bug in     `config.c::git_config_copy_or_rename_section_in_file()`. This bug can be used to inject arbitrary     configuration into a user's `$GIT_DIR/config` when attempting to remove the configuration section     associated with that submodule. When the attacker injects configuration values which specify executables     to run (such as `core.pager`, `core.editor`, `core.sshCommand`, etc.) this can lead to a remote code     execution. A fix A fix is available in versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8, 2.36.6,     2.37.7, 2.38.5, 2.39.3, and 2.40.1. As a workaround, avoid running `git submodule deinit` on untrusted     repositories or without prior inspection of any submodule sections in `$GIT_DIR/config`. (CVE-2023-29007)

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

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
175650	AlmaLinux 9 : git (ALSA-2023:2319)	Nessus	Alma Linux Local Security Checks	2023/5/14	2023/5/14	high
176176	AlmaLinux 8 : git (ALSA-2023:2859)	Nessus	Alma Linux Local Security Checks	2023/5/20	2023/5/20	high
177142	EulerOS Virtualization 3.0.6.0 : git (EulerOS-SA-2023-2238)	Nessus	Huawei Local Security Checks	2023/6/13	2023/6/13	critical
187314	GLSA-202312-15 : Git: Multiple Vulnerabilities	Nessus	Gentoo Local Security Checks	2023/12/27	2023/12/27	critical

检测

插件搜索

high

high

critical

critical