Vulnerability in libgit2 (UBUNTU-CVE-2020-12279)
Summary
Vulnerability in libgit2 (UBUNTU-CVE-2020-12279). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 0.24.1-2ubuntu0.2+esm2 or later.
Original description
The description as published by the source.
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.
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-2020-12279 has been found in libgit2.
Successful exploitation can lead to full system takeover.
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-2020-12279" on the vendor's site.
UBUNTU-CVE-2020-12279 (libgit2)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
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.
Check the vendor advisory for the affected versions of libgit2.
Severity: ?. Successful exploitation can lead to full system takeover.
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