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 host is affected by the vulnerability described in GLSA-202411-05 (libgit2: Multiple Vulnerabilities)

    Multiple vulnerabilities have been discovered in libgit2. Please review the CVE identifiers referenced     below for details.

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

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

The version of libgit2 / rust installed on the remote CBL Mariner 2.0 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the CVE-2023-22742 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 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.

    It was discovered that libgit2 mishandled equivalent filenames on NTFS partitions. If a user or automated     system were tricked into cloning a specially crafted repository, an attacker could possibly use this issue     to execute arbitrary code. This issue only affected Ubuntu 16.04 LTS and Ubuntu 18.04 LTS.
    (CVE-2020-12278, CVE-2020-12279)

    It was discovered that libgit2 did not perform certificate checking by default. An attacker could possibly     use this issue to perform a machine-in-the-middle attack. This issue only affected Ubuntu 16.04 LTS,     Ubuntu 18.04 LTS, Ubuntu 20.04 LTS, and Ubuntu 22.04 LTS. (CVE-2023-22742)

    It was discovered that libgit2 could be made to run into an infinite loop. An attacker could possibly use     this issue to cause a denial of service. This issue only affected Ubuntu 23.10. (CVE-2024-24575)

    It was discovered that libgit2 did not properly manage memory. An attacker could possibly use this issue     to cause a denial of service or execute arbitrary code. (CVE-2024-24577)

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.

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
210448	GLSA-202411-05 : libgit2: Multiple Vulnerabilities	Nessus	Gentoo Local Security Checks	medium
202348	CBL Mariner 2.0 Security Update: libgit2 / rust (CVE-2023-22742)	Nessus	MarinerOS Local Security Checks	medium
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

medium

medium

critical

medium

medium

medium

critical