USN-6678-1: libgit2 vulnerabilities
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)
Affected Software
Event History
Child vulnerabilities
Contains the following vulnerabilities.
Frequently Asked Questions
What is the severity of USN-6678-1?
USN-6678-1 has been classified as a potentially serious vulnerability due to its capability to execute arbitrary code.
How do I fix USN-6678-1?
To fix USN-6678-1, upgrade to the recommended versions of libgit2-1.5, libgit2-1.1, libgit2-28, libgit2-26, or libgit2-24 based on your Ubuntu version.
Which Ubuntu versions are affected by USN-6678-1?
USN-6678-1 affects Ubuntu 16.04 LTS, 18.04 LTS, 20.04 LTS, 22.04 LTS, and 23.10.
What is the impact of USN-6678-1?
The impact of USN-6678-1 is the potential execution of arbitrary code if a user clones a specially crafted repository.
Is there a workaround for USN-6678-1?
There is no official workaround for USN-6678-1, making it essential to apply the available security updates.