libgit2 is a cross-platform, linkable library implementation of Git. When using an SSH remote with the optional libssh2 backend, libgit2 does not perform certificate checking by default. Prior versions of libgit2 require the caller to set the `certificate_check` field of libgit2's `git_remote_callbacks` structure - if a certificate check callback is not set, libgit2 does not perform any certificate checking. This means that by default - without configuring a certificate check callback, clients will not perform validation on the server SSH keys and may be subject to a man-in-the-middle attack. Users are encouraged to upgrade to v1.4.5 or v1.5.1. Users unable to upgrade should ensure that all relevant certificates are manually checked.

The remote Redhat Enterprise Linux 7 host has one or more packages installed that are affected by multiple vulnerabilities that have been acknowledged by the vendor but will not be patched.

  - libgit2: NTFS protections inactive when running Git in the Windows Subsystem for Linux (CVE-2020-12279)

  - An issue was discovered in libgit2 before 0.28.4 and 0.9x before 0.99.0. path.c mishandles equivalent     filenames that exist because of NTFS Alternate Data Streams. This may allow remote code execution when     cloning a repository. This issue is similar to CVE-2019-1352. (CVE-2020-12278)

  - libgit2 is a cross-platform, linkable library implementation of Git. When using an SSH remote with the     optional libssh2 backend, libgit2 does not perform certificate checking by default. Prior versions of     libgit2 require the caller to set the `certificate_check` field of libgit2's `git_remote_callbacks`     structure - if a certificate check callback is not set, libgit2 does not perform any certificate checking.
    This means that by default - without configuring a certificate check callback, clients will not perform     validation on the server SSH keys and may be subject to a man-in-the-middle attack. Users are encouraged     to upgrade to v1.4.5 or v1.5.1. Users unable to upgrade should ensure that all relevant certificates are     manually checked. (CVE-2023-22742)

Note that Nessus has not tested for these issues but has instead relied on the package manager's report that the package is installed.

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

  - An issue was discovered in libgit2 before 0.28.4 and 0.9x before 0.99.0. path.c mishandles equivalent     filenames that exist because of NTFS Alternate Data Streams. This may allow remote code execution when     cloning a repository. This issue is similar to CVE-2019-1352. (CVE-2020-12278)

  - An issue was discovered in libgit2 before 0.28.4 and 0.9x before 0.99.0. checkout.c mishandles equivalent     filenames that exist because of NTFS short names. This may allow remote code execution when cloning a     repository. This issue is similar to CVE-2019-1353. (CVE-2020-12279)

  - libgit2 is a cross-platform, linkable library implementation of Git. When using an SSH remote with the     optional libssh2 backend, libgit2 does not perform certificate checking by default. Prior versions of     libgit2 require the caller to set the `certificate_check` field of libgit2's `git_remote_callbacks`     structure - if a certificate check callback is not set, libgit2 does not perform any certificate checking.
    This means that by default - without configuring a certificate check callback, clients will not perform     validation on the server SSH keys and may be subject to a man-in-the-middle attack. Users are encouraged     to upgrade to v1.4.5 or v1.5.1. Users unable to upgrade should ensure that all relevant certificates are     manually checked. (CVE-2023-22742)

  - libgit2 is a portable C implementation of the Git core methods provided as a linkable library with a solid     API, allowing to build Git functionality into your application. Using well-crafted inputs to     `git_revparse_single` can cause the function to enter an infinite loop, potentially causing a Denial of     Service attack in the calling application. The revparse function in `src/libgit2/revparse.c` uses a loop     to parse the user-provided spec string. There is an edge-case during parsing that allows a bad actor to     force the loop conditions to access arbitrary memory. Potentially, this could also leak memory if the     extracted rev spec is reflected back to the attacker. As such, libgit2 versions before 1.4.0 are not     affected. Users should upgrade to version 1.6.5 or 1.7.2. (CVE-2024-24575)

  - libgit2 is a portable C implementation of the Git core methods provided as a linkable library with a solid     API, allowing to build Git functionality into your application. Using well-crafted inputs to     `git_index_add` can cause heap corruption that could be leveraged for arbitrary code execution. There is     an issue in the `has_dir_name` function in `src/libgit2/index.c`, which frees an entry that should not be     freed. The freed entry is later used and overwritten with potentially bad actor-controlled data leading to     controlled heap corruption. Depending on the application that uses libgit2, this could lead to arbitrary     code execution. This issue has been patched in version 1.6.5 and 1.7.2. (CVE-2024-24577)

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

The remote SUSE Linux SLES15 / openSUSE 15 host has packages installed that are affected by a vulnerability as referenced in the SUSE-SU-2023:1909-1 advisory.

  - libgit2 is a cross-platform, linkable library implementation of Git. When using an SSH remote with the     optional libssh2 backend, libgit2 does not perform certificate checking by default. Prior versions of     libgit2 require the caller to set the `certificate_check` field of libgit2's `git_remote_callbacks`     structure - if a certificate check callback is not set, libgit2 does not perform any certificate checking.
    This means that by default - without configuring a certificate check callback, clients will not perform     validation on the server SSH keys and may be subject to a man-in-the-middle attack. Users are encouraged     to upgrade to v1.4.5 or v1.5.1. Users unable to upgrade should ensure that all relevant certificates are     manually checked. (CVE-2023-22742)

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

The remote SUSE Linux SLED15 / SLED_SAP15 / SLES15 / SLES_SAP15 / openSUSE 15 host has packages installed that are affected by a vulnerability as referenced in the SUSE-SU-2023:1788-1 advisory.

  - libgit2 is a cross-platform, linkable library implementation of Git. When using an SSH remote with the     optional libssh2 backend, libgit2 does not perform certificate checking by default. Prior versions of     libgit2 require the caller to set the `certificate_check` field of libgit2's `git_remote_callbacks`     structure - if a certificate check callback is not set, libgit2 does not perform any certificate checking.
    This means that by default - without configuring a certificate check callback, clients will not perform     validation on the server SSH keys and may be subject to a man-in-the-middle attack. Users are encouraged     to upgrade to v1.4.5 or v1.5.1. Users unable to upgrade should ensure that all relevant certificates are     manually checked. (CVE-2023-22742)

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

The remote openSUSE 15 host has packages installed that are affected by a vulnerability as referenced in the SUSE- SU-2023:1570-1 advisory.

  - libgit2 is a cross-platform, linkable library implementation of Git. When using an SSH remote with the     optional libssh2 backend, libgit2 does not perform certificate checking by default. Prior versions of     libgit2 require the caller to set the `certificate_check` field of libgit2's `git_remote_callbacks`     structure - if a certificate check callback is not set, libgit2 does not perform any certificate checking.
    This means that by default - without configuring a certificate check callback, clients will not perform     validation on the server SSH keys and may be subject to a man-in-the-middle attack. Users are encouraged     to upgrade to v1.4.5 or v1.5.1. Users unable to upgrade should ensure that all relevant certificates are     manually checked. (CVE-2023-22742)

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

The remote Debian 10 host has packages installed that are affected by multiple vulnerabilities as referenced in the dla-3340 advisory.

  - An issue was discovered in libgit2 before 0.28.4 and 0.9x before 0.99.0. path.c mishandles equivalent     filenames that exist because of NTFS Alternate Data Streams. This may allow remote code execution when     cloning a repository. This issue is similar to CVE-2019-1352. (CVE-2020-12278)

  - An issue was discovered in libgit2 before 0.28.4 and 0.9x before 0.99.0. checkout.c mishandles equivalent     filenames that exist because of NTFS short names. This may allow remote code execution when cloning a     repository. This issue is similar to CVE-2019-1353. (CVE-2020-12279)

  - libgit2 is a cross-platform, linkable library implementation of Git. When using an SSH remote with the     optional libssh2 backend, libgit2 does not perform certificate checking by default. Prior versions of     libgit2 require the caller to set the `certificate_check` field of libgit2's `git_remote_callbacks`     structure - if a certificate check callback is not set, libgit2 does not perform any certificate checking.
    This means that by default - without configuring a certificate check callback, clients will not perform     validation on the server SSH keys and may be subject to a man-in-the-middle attack. Users are encouraged     to upgrade to v1.4.5 or v1.5.1. Users unable to upgrade should ensure that all relevant certificates are     manually checked. (CVE-2023-22742)

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

ID	Name	Product	Family	Severity
195757	RHEL 7 : libgit2 (Unpatched Vulnerability)	Nessus	Red Hat Local Security Checks	critical
191559	Ubuntu 16.04 LTS / 18.04 LTS / 20.04 LTS / 22.04 LTS / 23.10 : libgit2 vulnerabilities (USN-6678-1)	Nessus	Ubuntu Local Security Checks	critical
174493	SUSE SLES15 / openSUSE 15 Security Update : libgit2 (SUSE-SU-2023:1909-1)	Nessus	SuSE Local Security Checks	medium
174011	SUSE SLED15 / SLES15 / openSUSE 15 Security Update : libgit2 (SUSE-SU-2023:1788-1)	Nessus	SuSE Local Security Checks	medium
173410	openSUSE 15 Security Update : libgit2 (SUSE-SU-2023:1570-1)	Nessus	SuSE Local Security Checks	medium
171871	Debian DLA-3340-1 : libgit2 - LTS security update	Nessus	Debian Local Security Checks	critical

Detections

Analytics

CVE-2023-22742

medium

Tenable Plugins

critical

critical

medium

medium

medium

critical