Alerts This Week
Warning Icon 1 1,082
Alerts This Week
Warning Icon 1 1,082

Gentoo: GLSA-202411-05 high: libgit2 multiple vulnerabilities

gentoo
Calendar Grey November 6, 2024
Dist Gentoo Esm H88
Several libgit2 security flaws noted in Gentoo GLSA 202411-05 necessitate immediate action due to significant security threats.
Multiple vulnerabilities have been discovered in libgit2, the worst of which could lead to arbitrary code execution.

Summary

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

Resolution

All libgit2 users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=dev-libs/libgit2-1.7.2"

References

[ 1 ] CVE-2023-22742 https://nvd.nist.gov/vuln/detail/CVE-2023-22742

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website:
https://security.gentoo.org/glsa/202411-05
style>.gentoo_availability{display:block;}

Concerns

Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users' machines is of utmost importance to us. Any security concerns should be addressed to security@gentoo.org or alternatively, you may file a bug at https://bugs.gentoo.org.

Severity: High
Title: libgit2: Multiple Vulnerabilities
Date: November 06, 2024
Bugs: #891525, #923971
ID: 202411-05

Synopsis

Multiple vulnerabilities have been discovered in libgit2, the worst of which could lead to arbitrary code execution.

Background

libgit2 is a portable, pure C implementation of the Git core methods provided as a re-entrant linkable library with a solid API, allowing you to write native speed custom Git applications in any language that supports C bindings.

Get the latest News and Insights

Get the latest Linux and open source security news straight to your inbox.

Affected Packages

Package Vulnerable Unaffected ---------------- ------------ ------------ dev-libs/libgit2 < 1.7.2 >= 1.7.2

Impact

Please review the referenced CVE identifiers for details.

Workaround

There is no known workaround at this time.

Your message here