Vulnerability in git (CLSA-2025-1754939766)

Summary

vulnerability in git (CLSA-2025-1754939766). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `2.27.0-1.el8.tuxcare.els9` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CLSA-2025-1754939766** has been found in git. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade git to **2.27.0-1.el8.tuxcare.els9** or later. If unsure, ask your IT team or search "git CLSA-2025-1754939766" on the vendor's site.

CLSA-2025-1754939766 (git) — Patched: `2.27.0-1.el8.tuxcare.els9` — 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.

❓ What is the problem

**A vulnerability** (unclassified) exists in git.

📍 Affected scope

git — .

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure

🔧 How to fix

Update to **2.27.0-1.el8.tuxcare.els9**.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

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 (7 steps)

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'git' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `git` を grep し、稼働しているサービス・バージョンを把握する。
6
Apply patch patch
```
Upgrade git to 2.27.0-1.el8.tuxcare.els9
```
ステージング環境で 2.27.0-1.el8.tuxcare.els9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
7
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。