Vulnerability in libgit2 (UBUNTU-CVE-2024-24577)
Summary
Vulnerability in libgit2 (UBUNTU-CVE-2024-24577). Confidential information can be exposed externally. Exploitable via git_index_add. Mitigation: upgrade to 0.24.1-2ubuntu0.2+esm2 or later.
Original description
The description as published by the source.
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.
Source: OSV.dev (Open Source Vulnerabilities) OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as UBUNTU-CVE-2024-24577 has been found in libgit2.
Attackers can target a specific entry point like git_index_add over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade libgit2 to 0.24.1-2ubuntu0.2+esm2 or later.
If unsure, ask your IT team or search "libgit2 UBUNTU-CVE-2024-24577" on the vendor's site.
UBUNTU-CVE-2024-24577 (libgit2)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: git_index_add / has_dir_name
Patched: 0.24.1-2ubuntu0.2+esm2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (unclassified) exists in libgit2. Attackers reach the vulnerable code path via git_index_add without authentication.
Check the vendor advisory for the affected versions of libgit2. Attack surface: git_index_add / has_dir_name.
Severity: ?. Confidential information can be exposed externally.
Update to 0.24.1-2ubuntu0.2+esm2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'libgit2' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'libgit2' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
libgit2を grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade libgit2 to 0.24.1-2ubuntu0.2+esm2ステージング環境で 0.24.1-2ubuntu0.2+esm2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory ubuntu.com
- report ubuntu.com
- report github.com
- report github.com
- report github.com
- report cve.org