The remote Redhat Enterprise Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2024:6028 advisory.

    Git is a distributed revision control system with a decentralized architecture. As opposed to centralized     version control systems with a client-server model, Git ensures that each working copy of a Git repository     is an exact copy with complete revision history. This not only allows the user to work on and contribute     to projects without the need to have permission to push the changes to their official repositories, but     also makes it possible for the user to work with no network connection.

    Security Fix(es):

    * git: Recursive clones RCE (CVE-2024-32002)

    * git: RCE while cloning local repos (CVE-2024-32004)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

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

The version of git installed on the remote host is prior to 2.39.4 / 2.45.1. It is, therefore, affected by multiple vulnerabilities as referenced in the SSA:2024-136-02 advisory.

  - Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and     2.39.4, repositories with submodules can be crafted in a way that exploits a bug in Git whereby it can be     fooled into writing files not into the submodule's worktree but into a `.git/` directory. This allows     writing a hook that will be executed while the clone operation is still running, giving the user no     opportunity to inspect the code that is being executed. The problem has been patched in versions 2.45.1,     2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4. If symbolic link support is disabled in Git (e.g. via     `git config --global core.symlinks false`), the described attack won't work. As always, it is best to     avoid cloning repositories from untrusted sources. (CVE-2024-32002)

  - Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and     2.39.4, an attacker can prepare a local repository in such a way that, when cloned, will execute arbitrary     code during the operation. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2,     2.41.1, 2.40.2, and 2.39.4. As a workaround, avoid cloning repositories from untrusted sources.
    (CVE-2024-32004)

  - Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and     2.39.4, local clones may end up hardlinking files into the target repository's object database when source     and target repository reside on the same disk. If the source repository is owned by a different user, then     those hardlinked files may be rewritten at any point in time by the untrusted user. Cloning local     repositories will cause Git to either copy or hardlink files of the source repository into the target     repository. This significantly speeds up such local clones compared to doing a proper clone and saves     both disk space and compute time. When cloning a repository located on the same disk that is owned by a     different user than the current user we also end up creating such hardlinks. These files will continue to     be owned and controlled by the potentially-untrusted user and can be rewritten by them at will in the     future. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and     2.39.4. (CVE-2024-32020)

  - Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and     2.39.4, when cloning a local source repository that contains symlinks via the filesystem, Git may create     hardlinks to arbitrary user-readable files on the same filesystem as the target repository in the     `objects/` directory. Cloning a local repository over the filesystem may creating hardlinks to arbitrary     user-owned files on the same filesystem in the target Git repository's `objects/` directory. When cloning     a repository over the filesystem (without explicitly specifying the `file://` protocol or `--no-local`),     the optimizations for local cloning will be used, which include attempting to hard link the object files     instead of copying them. While the code includes checks against symbolic links in the source repository,     which were added during the fix for CVE-2022-39253, these checks can still be raced because the hard link     operation ultimately follows symlinks. If the object on the filesystem appears as a file during the check,     and then a symlink during the operation, this will allow the adversary to bypass the check and create     hardlinks in the destination objects directory to arbitrary, user-readable files. The problem has been     patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4. (CVE-2024-32021)

  - Git is a revision control system. The Git project recommends to avoid working in untrusted repositories,     and instead to clone it first with `git clone --no-local` to obtain a clean copy. Git has specific     protections to make that a safe operation even with an untrusted source repository, but vulnerabilities     allow those protections to be bypassed. In the context of cloning local repositories owned by other users,     this vulnerability has been covered in CVE-2024-32004. But there are circumstances where the fixes for     CVE-2024-32004 are not enough: For example, when obtaining a `.zip` file containing a full copy of a Git     repository, it should not be trusted by default to be safe, as e.g. hooks could be configured to run     within the context of that repository. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4,     2.42.2, 2.41.1, 2.40.2, and 2.39.4. As a workaround, avoid using Git in repositories that have been     obtained via archives from untrusted sources. (CVE-2024-32465)

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

The remote MiracleLinux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the AXSA:2024-8477:08 advisory.

    * git: Recursive clones RCE (CVE-2024-32002)
      * git: RCE while cloning local repos (CVE-2024-32004)
      * git: additional local RCE (CVE-2024-32465)
      * git: insecure hardlinks (CVE-2024-32020)
      * git: symlink bypass (CVE-2024-32021)

Tenable has extracted the preceding description block directly from the MiracleLinux security advisory.

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

The Rocky Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the CIQ crlsa-2024_4083 advisory.

    * git: Recursive clones RCE (CVE-2024-32002)

    * git: RCE while cloning local repos (CVE-2024-32004)

    * git: additional local RCE (CVE-2024-32465)

    * git: insecure hardlinks (CVE-2024-32020)

    * git: symlink bypass (CVE-2024-32021)

Tenable has extracted the preceding description block directly from the CIQ security advisory.

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

The remote Ubuntu 16.04 LTS / 18.04 LTS host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-7023-1 advisory.

    Maxime Escourbiac and Yassine Bengana discovered that Git incorrectly handled some gettext machinery. An     attacker could possibly use this issue to allows the malicious placement of crafted messages. This issue     was fixed in Ubuntu 16.04 LTS. (CVE-2023-25815)

    It was discovered that Git incorrectly handled certain submodules. An attacker could possibly use this     issue to execute arbitrary code. This issue was fixed in Ubuntu 18.04 LTS. (CVE-2024-32002)

    It was discovered that Git incorrectly handled certain cloned repositories. An attacker could possibly use     this issue to execute arbitrary code. This issue was fixed in Ubuntu 18.04 LTS. (CVE-2024-32004,     CVE-2024-32465)

    It was discovered that Git incorrectly handled local clones with hardlinked files/directories. An attacker     could possibly use this issue to place a specialized repository on their targets local system. This     issue was fixed in Ubuntu 18.04 LTS. (CVE-2024-32020)

    It was discovered that Git incorrectly handled certain symlinks. An attacker could possibly use this issue     to impact availability and integrity creating hardlinked arbitrary files into users repositorys     objects/directory. This issue was fixed in Ubuntu 18.04 LTS. (CVE-2024-32021)

Tenable has extracted the preceding description block directly from the Ubuntu security advisory.

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

An update of the git package has been released.

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

    Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and     2.39.4, repositories with submodules can be crafted in a way that exploits a bug in Git whereby it can be     fooled into writing files not into the submodule's worktree but into a `.git/` directory. This allows     writing a hook that will be executed while the clone operation is still running, giving the user no     opportunity to inspect the code that is being executed. The problem has been patched in versions 2.45.1,     2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4. If symbolic link support is disabled in Git (e.g. via     `git config --global core.symlinks false`), the described attack won't work. As always, it is best to     avoid cloning repositories from untrusted sources.(CVE-2024-32002)

    Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and     2.39.4, local clones may end up hardlinking files into the target repository's object database when source     and target repository reside on the same disk. If the source repository is owned by a different user, then     those hardlinked files may be rewritten at any point in time by the untrusted user. Cloning local     repositories will cause Git to either copy or hardlink files of the source repository into the target     repository. This significantly speeds up such local clones compared to doing a 'proper' clone and saves     both disk space and compute time. When cloning a repository located on the same disk that is owned by a     different user than the current user we also end up creating such hardlinks. These files will continue to     be owned and controlled by the potentially-untrusted user and can be rewritten by them at will in the     future. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and     2.39.4.(CVE-2024-32020)

    Git is a revision control system. The Git project recommends to avoid working in untrusted repositories,     and instead to clone it first with `git clone --no-local` to obtain a clean copy. Git has specific     protections to make that a safe operation even with an untrusted source repository, but vulnerabilities     allow those protections to be bypassed. In the context of cloning local repositories owned by other users,     this vulnerability has been covered in CVE-2024-32004. But there are circumstances where the fixes for     CVE-2024-32004 are not enough: For example, when obtaining a `.zip` file containing a full copy of a Git     repository, it should not be trusted by default to be safe, as e.g. hooks could be configured to run     within the context of that repository. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4,     2.42.2, 2.41.1, 2.40.2, and 2.39.4. As a workaround, avoid using Git in repositories that have been     obtained via archives from untrusted sources.(CVE-2024-32465)

    Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and     2.39.4, an attacker can prepare a local repository in such a way that, when cloned, will execute arbitrary     code during the operation. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2,     2.41.1, 2.40.2, and 2.39.4. As a workaround, avoid cloning repositories from untrusted     sources.(CVE-2024-32004)

    Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and     2.39.4, when cloning a local source repository that contains symlinks via the filesystem, Git may create     hardlinks to arbitrary user-readable files on the same filesystem as the target repository in the     `objects/` directory. Cloning a local repository over the filesystem may creating hardlinks to arbitrary     user-owned files on the same filesystem in the target Git repository's `objects/` directory. When cloning     a repository over the filesystem (without explicitly specifying the `file://` protocol or `--no-local`),     the optimizations for local cloning will be used, which include attempting to hard link the object files     instead of copying them. While the code includes checks against symbolic links in the source repository,     which were added during the fix for CVE-2022-39253, these checks can still be raced because the hard link     operation ultimately follows symlinks. If the object on the filesystem appears as a file during the check,     and then a symlink during the operation, this will allow the adversary to bypass the check and create     hardlinks in the destination objects directory to arbitrary, user-readable files. The problem has been     patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4.(CVE-2024-32021)

Tenable has extracted the preceding description block directly from the EulerOS git security advisory.

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

The remote Redhat Enterprise Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2024:6610 advisory.

    Git is a distributed revision control system with a decentralized architecture. As opposed to centralized     version control systems with a client-server model, Git ensures that each working copy of a Git repository     is an exact copy with complete revision history. This not only allows the user to work on and contribute     to projects without the need to have permission to push the changes to their official repositories, but     also makes it possible for the user to work with no network connection.

    Security Fix(es):

    * git: Recursive clones RCE (CVE-2024-32002)

    * git: RCE while cloning local repos (CVE-2024-32004)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

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 installation on the remote host is affected by the following vulnerabilities :

    Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and     2.39.4, repositories with submodules can be crafted in a way that exploits a bug in Git whereby it can be     fooled into writing files not into the submodule's worktree but into a `.git/` directory. This allows     writing a hook that will be executed while the clone operation is still running, giving the user no     opportunity to inspect the code that is being executed. The problem has been patched in versions 2.45.1,     2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4. If symbolic link support is disabled in Git (e.g. via     `git config --global core.symlinks false`), the described attack won't work. As always, it is best to     avoid cloning repositories from untrusted sources.(CVE-2024-32002)

    Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and     2.39.4, an attacker can prepare a local repository in such a way that, when cloned, will execute arbitrary     code during the operation. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2,     2.41.1, 2.40.2, and 2.39.4. As a workaround, avoid cloning repositories from untrusted     sources.(CVE-2024-32004)

    Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and     2.39.4, local clones may end up hardlinking files into the target repository's object database when source     and target repository reside on the same disk. If the source repository is owned by a different user, then     those hardlinked files may be rewritten at any point in time by the untrusted user. Cloning local     repositories will cause Git to either copy or hardlink files of the source repository into the target     repository. This significantly speeds up such local clones compared to doing a 'proper' clone and saves     both disk space and compute time. When cloning a repository located on the same disk that is owned by a     different user than the current user we also end up creating such hardlinks. These files will continue to     be owned and controlled by the potentially-untrusted user and can be rewritten by them at will in the     future. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and     2.39.4.(CVE-2024-32020)

    Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and     2.39.4, when cloning a local source repository that contains symlinks via the filesystem, Git may create     hardlinks to arbitrary user-readable files on the same filesystem as the target repository in the     `objects/` directory. Cloning a local repository over the filesystem may creating hardlinks to arbitrary     user-owned files on the same filesystem in the target Git repository's `objects/` directory. When cloning     a repository over the filesystem (without explicitly specifying the `file://` protocol or `--no-local`),     the optimizations for local cloning will be used, which include attempting to hard link the object files     instead of copying them. While the code includes checks against symbolic links in the source repository,     which were added during the fix for CVE-2022-39253, these checks can still be raced because the hard link     operation ultimately follows symlinks. If the object on the filesystem appears as a file during the check,     and then a symlink during the operation, this will allow the adversary to bypass the check and create     hardlinks in the destination objects directory to arbitrary, user-readable files. The problem has been     patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4.(CVE-2024-32021)

    Git is a revision control system. The Git project recommends to avoid working in untrusted repositories,     and instead to clone it first with `git clone --no-local` to obtain a clean copy. Git has specific     protections to make that a safe operation even with an untrusted source repository, but vulnerabilities     allow those protections to be bypassed. In the context of cloning local repositories owned by other users,     this vulnerability has been covered in CVE-2024-32004. But there are circumstances where the fixes for     CVE-2024-32004 are not enough: For example, when obtaining a `.zip` file containing a full copy of a Git     repository, it should not be trusted by default to be safe, as e.g. hooks could be configured to run     within the context of that repository. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4,     2.42.2, 2.41.1, 2.40.2, and 2.39.4. As a workaround, avoid using Git in repositories that have been     obtained via archives from untrusted sources.(CVE-2024-32465)

Tenable has extracted the preceding description block directly from the EulerOS git security advisory.

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

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2024-623 advisory.

    Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and     2.39.4, repositories with submodules can be crafted in a way that exploits a bug in Git whereby it can be     fooled into writing files not into the submodule's worktree but into a `.git/` directory. This allows     writing a hook that will be executed while the clone operation is still running, giving the user no     opportunity to inspect the code that is being executed. The problem has been patched in versions 2.45.1,     2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4. If symbolic link support is disabled in Git (e.g. via     `git config --global core.symlinks false`), the described attack won't work. As always, it is best to     avoid cloning repositories from untrusted sources. (CVE-2024-32002)

    Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and     2.39.4, an attacker can prepare a local repository in such a way that, when cloned, will execute arbitrary     code during the operation. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2,     2.41.1, 2.40.2, and 2.39.4. As a workaround, avoid cloning repositories from untrusted sources.
    (CVE-2024-32004)

    Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and     2.39.4, local clones may end up hardlinking files into the target repository's object database when source     and target repository reside on the same disk. If the source repository is owned by a different user, then     those hardlinked files may be rewritten at any point in time by the untrusted user. Cloning local     repositories will cause Git to either copy or hardlink files of the source repository into the target     repository. This significantly speeds up such local clones compared to doing a proper clone and saves     both disk space and compute time. When cloning a repository located on the same disk that is owned by a     different user than the current user we also end up creating such hardlinks. These files will continue to     be owned and controlled by the potentially-untrusted user and can be rewritten by them at will in the     future. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and     2.39.4. (CVE-2024-32020)

    Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and     2.39.4, when cloning a local source repository that contains symlinks via the filesystem, Git may create     hardlinks to arbitrary user-readable files on the same filesystem as the target repository in the     `objects/` directory. Cloning a local repository over the filesystem may creating hardlinks to arbitrary     user-owned files on the same filesystem in the target Git repository's `objects/` directory. When cloning     a repository over the filesystem (without explicitly specifying the `file://` protocol or `--no-local`),     the optimizations for local cloningwill be used, which include attempting to hard link the object files     instead of copying them. While the code includes checks against symbolic links in the source repository,     which were added during the fix for CVE-2022-39253, these checks can still be raced because the hard link     operation ultimately follows symlinks. If the object on the filesystem appears as a file during the check,     and then a symlink during the operation, this will allow the adversary to bypass the check and create     hardlinks in the destination objects directory to arbitrary, user-readable files. The problem has been     patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4. (CVE-2024-32021)

    Git is a revision control system. The Git project recommends to avoid working in untrusted repositories,     and instead to clone it first with `git clone --no-local` to obtain a clean copy. Git has specific     protections to make that a safe operation even with an untrusted source repository, but vulnerabilities     allow those protections to be bypassed. In the context of cloning local repositories owned by other users,     this vulnerability has been covered in CVE-2024-32004. But there are circumstances where the fixes for     CVE-2024-32004 are not enough: For example, when obtaining a `.zip` file containing a full copy of a Git     repository, it should not be trusted by default to be safe, as e.g. hooks could be configured to run     within the context of that repository. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4,     2.42.2, 2.41.1, 2.40.2, and 2.39.4. As a workaround, avoid using Git in repositories that have been     obtained via archives from untrusted sources. (CVE-2024-32465)

Tenable has extracted the preceding description block directly from the tested product security advisory.

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

The version of git installed on the remote host is prior to 2.38.4-1.81. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS-2024-1939 advisory.

    Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and     2.39.4, repositories with submodules can be crafted in a way that exploits a bug in Git whereby it can be     fooled into writing files not into the submodule's worktree but into a `.git/` directory. This allows     writing a hook that will be executed while the clone operation is still running, giving the user no     opportunity to inspect the code that is being executed. The problem has been patched in versions 2.45.1,     2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4. If symbolic link support is disabled in Git (e.g. via     `git config --global core.symlinks false`), the described attack won't work. As always, it is best to     avoid cloning repositories from untrusted sources. (CVE-2024-32002)

    Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and     2.39.4, an attacker can prepare a local repository in such a way that, when cloned, will execute arbitrary     code during the operation. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2,     2.41.1, 2.40.2, and 2.39.4. As a workaround, avoid cloning repositories from untrusted sources.
    (CVE-2024-32004)

    Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and     2.39.4, local clones may end up hardlinking files into the target repository's object database when source     and target repository reside on the same disk. If the source repository is owned by a different user, then     those hardlinked files may be rewritten at any point in time by the untrusted user. Cloning local     repositories will cause Git to either copy or hardlink files of the source repository into the target     repository. This significantly speeds up such local clones compared to doing a proper clone and saves     both disk space and compute time. When cloning a repository located on the same disk that is owned by a     different user than the current user we also end up creating such hardlinks. These files will continue to     be owned and controlled by the potentially-untrusted user and can be rewritten by them at will in the     future. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and     2.39.4. (CVE-2024-32020)

    Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and     2.39.4, when cloning a local source repository that contains symlinks via the filesystem, Git may create     hardlinks to arbitrary user-readable files on the same filesystem as the target repository in the     `objects/` directory. Cloning a local repository over the filesystem may creating hardlinks to arbitrary     user-owned files on the same filesystem in the target Git repository's `objects/` directory. When cloning     a repository over the filesystem (without explicitly specifying the `file://` protocol or `--no-local`),     the optimizations for local cloningwill be used, which include attempting to hard link the object files     instead of copying them. While the code includes checks against symbolic links in the source repository,     which were added during the fix for CVE-2022-39253, these checks can still be raced because the hard link     operation ultimately follows symlinks. If the object on the filesystem appears as a file during the check,     and then a symlink during the operation, this will allow the adversary to bypass the check and create     hardlinks in the destination objects directory to arbitrary, user-readable files. The problem has been     patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4. (CVE-2024-32021)

    Git is a revision control system. The Git project recommends to avoid working in untrusted repositories,     and instead to clone it first with `git clone --no-local` to obtain a clean copy. Git has specific     protections to make that a safe operation even with an untrusted source repository, but vulnerabilities     allow those protections to be bypassed. In the context of cloning local repositories owned by other users,     this vulnerability has been covered in CVE-2024-32004. But there are circumstances where the fixes for     CVE-2024-32004 are not enough: For example, when obtaining a `.zip` file containing a full copy of a Git     repository, it should not be trusted by default to be safe, as e.g. hooks could be configured to run     within the context of that repository. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4,     2.42.2, 2.41.1, 2.40.2, and 2.39.4. As a workaround, avoid using Git in repositories that have been     obtained via archives from untrusted sources. (CVE-2024-32465)

Tenable has extracted the preceding description block directly from the tested product security advisory.

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

The remote Redhat Enterprise Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2024:4084 advisory.

    Git is a distributed revision control system with a decentralized architecture. As opposed to centralized     version control systems with a client-server model, Git ensures that each working copy of a Git repository     is an exact copy with complete revision history. This not only allows the user to work on and contribute     to projects without the need to have permission to push the changes to their official repositories, but     also makes it possible for the user to work with no network connection.

    Security Fix(es):

    * git: Recursive clones RCE (CVE-2024-32002)

    * git: RCE while cloning local repos (CVE-2024-32004)

    * git: additional local RCE (CVE-2024-32465)

    * git: insecure hardlinks (CVE-2024-32020)

    * git: symlink bypass (CVE-2024-32021)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer the CVE page(s) listed in the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

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

The remote Oracle Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the ELSA-2024-4083 advisory.

    [2.43.5-1]
    - Update to 2.43.5
    - Related: RHEL-36402, RHEL-36414

    [2.43.4-1]
    - Update to 2.43.4
    - Resolves: RHEL-36402, RHEL-36414

Tenable has extracted the preceding description block directly from the Oracle Linux security advisory.

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

The remote Alibaba Cloud Linux 3 host has packages installed that are affected by multiple vulnerabilities as referenced in the ALINUX3-SA-2024:0148 advisory.

    Package updates are available for Alibaba Cloud Linux 3 that fix the following vulnerabilities:

    CVE-2024-32002:
    Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and     2.39.4, repositories with submodules can be crafted in a way that exploits a bug in Git whereby it can be     fooled into writing files not into the submodule's worktree but into a `.git/` directory. This allows     writing a hook that will be executed while the clone operation is still running, giving the user no     opportunity to inspect the code that is being executed. The problem has been patched in versions 2.45.1,     2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4. If symbolic link support is disabled in Git (e.g. via     `git config --global core.symlinks false`), the described attack won't work. As always, it is best to     avoid cloning repositories from untrusted sources.

    CVE-2024-32004:
    Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and     2.39.4, an attacker can prepare a local repository in such a way that, when cloned, will execute arbitrary     code during the operation. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2,     2.41.1, 2.40.2, and 2.39.4. As a workaround, avoid cloning repositories from untrusted sources.

    CVE-2024-32020:
    Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and     2.39.4, local clones may end up hardlinking files into the target repository's object database when source     and target repository reside on the same disk. If the source repository is owned by a different user, then     those hardlinked files may be rewritten at any point in time by the untrusted user. Cloning local     repositories will cause Git to either copy or hardlink files of the source repository into the target     repository. This significantly speeds up such local clones compared to doing a proper clone and saves     both disk space and compute time. When cloning a repository located on the same disk that is owned by a     different user than the current user we also end up creating such hardlinks. These files will continue to     be owned and controlled by the potentially-untrusted user and can be rewritten by them at will in the     future. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and     2.39.4.

    CVE-2024-32021:
    Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and     2.39.4, when cloning a local source repository that contains symlinks via the filesystem, Git may create     hardlinks to arbitrary user-readable files on the same filesystem as the target repository in the     `objects/` directory. Cloning a local repository over the filesystem may creating hardlinks to arbitrary     user-owned files on the same filesystem in the target Git repository's `objects/` directory. When cloning     a repository over the filesystem (without explicitly specifying the `file://` protocol or `--no-local`),     the optimizations for local cloning     will be used, which include attempting to hard link the object files instead of copying them. While the     code includes checks against symbolic links in the source repository, which were added during the fix for     CVE-2022-39253, these checks can still be raced because the hard link operation ultimately follows     symlinks. If the object on the filesystem appears as a file during the check, and then a symlink during     the operation, this will allow the adversary to bypass the check and create hardlinks in the destination     objects directory to arbitrary, user-readable files. The problem has been patched in versions 2.45.1,     2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4.

    CVE-2024-32465:
    Git is a revision control system. The Git project recommends to avoid working in untrusted repositories,     and instead to clone it first with `git clone --no-local` to obtain a clean copy. Git has specific     protections to make that a safe operation even with an untrusted source repository, but vulnerabilities     allow those protections to be bypassed. In the context of cloning local repositories owned by other users,     this vulnerability has been covered in CVE-2024-32004. But there are circumstances where the fixes for     CVE-2024-32004 are not enough: For example, when obtaining a `.zip` file containing a full copy of a Git     repository, it should not be trusted by default to be safe, as e.g. hooks could be configured to run     within the context of that repository. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4,     2.42.2, 2.41.1, 2.40.2, and 2.39.4. As a workaround, avoid using Git in repositories that have been     obtained via archives from untrusted sources.

Tenable has extracted the preceding description block directly from the Alibaba Cloud Linux security advisory.

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

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
206311	RHEL 8 : git (RHSA-2024:6028)	Nessus	Red Hat Local Security Checks	2024/8/29	2024/11/7	critical
197168	Slackware Linux 15.0 / current git Multiple Vulnerabilities (SSA:2024-136-02)	Nessus	Slackware Local Security Checks	2024/5/16	2024/5/20	critical
293684	MiracleLinux 8 : git-2.43.5-1.el8_10 (AXSA:2024-8477:08)	Nessus	Miracle Linux Local Security Checks	2026/1/20	2026/1/20	critical
356169	Rocky Linux 9 [CIQ] Security Update: git / git-all / git-core / git-core-debuginfo / git-core-doc / etc Multiple Vulnerabilities (crlsa-2024_4083)	Nessus	Rocky Linux Local Security Checks	2026/10/1	2026/10/1	critical
207439	Ubuntu 16.04 LTS / 18.04 LTS : Git vulnerabilities (USN-7023-1)	Nessus	Ubuntu Local Security Checks	2024/9/19	2024/9/19	critical
204442	Photon OS 4.0: Git PHSA-2024-4.0-0611	Nessus	PhotonOS Local Security Checks	2024/7/24	2026/11/2	critical
206937	EulerOS 2.0 SP12 : git (EulerOS-SA-2024-2350)	Nessus	Huawei Local Security Checks	2024/9/10	2024/9/10	critical
206994	RHEL 9 : git (RHSA-2024:6610)	Nessus	Red Hat Local Security Checks	2024/9/11	2024/11/7	critical
207160	EulerOS 2.0 SP9 : git (EulerOS-SA-2024-2365)	Nessus	Huawei Local Security Checks	2024/9/12	2024/9/12	critical
205248	EulerOS 2.0 SP11 : git (EulerOS-SA-2024-2081)	Nessus	Huawei Local Security Checks	2024/8/8	2024/8/8	critical
197965	Amazon Linux 2023 : git, git-all, git-core (ALAS2023-2024-623)	Nessus	Amazon Linux Local Security Checks	2024/5/28	2024/12/11	critical
200102	Amazon Linux AMI : git (ALAS-2024-1939)	Nessus	Amazon Linux Local Security Checks	2024/6/5	2024/12/11	critical
200983	RHEL 8 : git (RHSA-2024:4084)	Nessus	Red Hat Local Security Checks	2024/6/25	2024/11/7	critical
201001	Oracle Linux 9 : git (ELSA-2024-4083)	Nessus	Oracle Linux Local Security Checks	2024/6/25	2025/9/9	critical
235942	Alibaba Cloud Linux 3 : 0148: git (ALINUX3-SA-2024:0148)	Nessus	Alibaba Cloud Linux Local Security Checks	2025/5/14	2025/5/14	critical

检测

插件搜索

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical