Vulnerability in git (ALPINE-CVE-2021-40330)
Summary
Vulnerability in git (ALPINE-CVE-2021-40330). Confidential information can be exposed externally. Mitigation: upgrade to 2.26.3-r1 or later.
Original description
The description as published by the source.
git_connect_git in connect.c in Git before 2.30.1 allows a repository path to contain a newline character, which may result in unexpected cross-protocol requests, as demonstrated by the git://localhost:1234/%0d%0a%0d%0aGET%20/%20HTTP/1.1 substring.
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 ALPINE-CVE-2021-40330 has been found in git.
Confidential information can be exposed externally.
What to do: upgrade git to 2.26.3-r1 or later.
If unsure, ask your IT team or search "git ALPINE-CVE-2021-40330" on the vendor's site.
ALPINE-CVE-2021-40330 (git)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.26.3-r1 — 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 git.
Check the vendor advisory for the affected versions of git.
Severity: ?. Confidential information can be exposed externally.
Update to 2.26.3-r1.
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 'git' . 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 'git' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
gitを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade git to 2.26.3-r1ステージング環境で 2.26.3-r1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory security.alpinelinux.org