Vulnerability in libgit2 (UBUNTU-CVE-2023-22742)
Summary
Vulnerability in libgit2 (UBUNTU-CVE-2023-22742). Data can be tampered with by attackers. Exploitable via certificate_check. Mitigation: upgrade to 0.24.1-2ubuntu0.2+esm2 or later.
Original description
The description as published by the source.
libgit2 is a cross-platform, linkable library implementation of Git. When using an SSH remote with the optional libssh2 backend, libgit2 does not perform certificate checking by default. Prior versions of libgit2 require the caller to set the certificate_check field of libgit2's git_remote_callbacks structure - if a certificate check callback is not set, libgit2 does not perform any certificate checking. This means that by default - without configuring a certificate check callback, clients will not perform validation on the server SSH keys and may be subject to a man-in-the-middle attack. Users are encouraged to upgrade to v1.4.5 or v1.5.1. Users unable to upgrade should ensure that all relevant certificates are manually checked.
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-2023-22742 has been found in libgit2.
Attackers can target a specific entry point like certificate_check over the network to misuse the product.
Data can be tampered with by attackers.
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-2023-22742" on the vendor's site.
UBUNTU-CVE-2023-22742 (libgit2)
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: certificate_check / git_remote_callbacks
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 certificate_check without authentication.
Check the vendor advisory for the affected versions of libgit2. Attack surface: certificate_check / git_remote_callbacks.
Severity: ?. Data can be tampered with by attackers.
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 libssh2.org
- report cve.org