Vulnerability in libgit2 (UBUNTU-CVE-2018-15501)
Summary
Vulnerability in libgit2 (UBUNTU-CVE-2018-15501). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.19.0-2ubuntu0.4+esm2 or later.
Original description
The description as published by the source.
In ng_pkt in transports/smart_pkt.c in libgit2 before 0.26.6 and 0.27.x before 0.27.4, a remote attacker can send a crafted smart-protocol "ng" packet that lacks a '\0' byte to trigger an out-of-bounds read that leads to DoS.
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-2018-15501 has been found in libgit2.
Risk of unauthorized operations or information disclosure.
What to do: upgrade libgit2 to 0.19.0-2ubuntu0.4+esm2 or later.
If unsure, ask your IT team or search "libgit2 UBUNTU-CVE-2018-15501" on the vendor's site.
UBUNTU-CVE-2018-15501 (libgit2)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 0.19.0-2ubuntu0.4+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: ?. Risk of unauthorized operations or information disclosure.
Update to 0.19.0-2ubuntu0.4+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.19.0-2ubuntu0.4+esm2ステージング環境で 0.19.0-2ubuntu0.4+esm2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory ubuntu.com
- report ubuntu.com
- report bugs.chromium.org
- report github.com
- report bugzilla.suse.com
- report github.com
- report github.com
- report pro-linux.de
- report cve.org