← Back
GHSA-539m-9xh6-q6rr
Vulnerability in GitPython (GHSA-539m-9xh6-q6rr)
Summary
vulnerability in GitPython (GHSA-539m-9xh6-q6rr). Risk of unauthorized operations or information disclosure. Exploitable via `GET /internal-metadata`. Mitigation: upgrade to `3.1.57` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-539m-9xh6-q6rr** has been found in GitPython.
Attackers can target a specific entry point like `GET /internal-metadata` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade GitPython to **3.1.57** or later.
If unsure, ask your IT team or search "GitPython GHSA-539m-9xh6-q6rr" on the vendor's site.
GHSA-539m-9xh6-q6rr (GitPython) — CWE-73 /
Attack surface: GET /internal-metadata / `transform_kwargs` / `unsafe_git_clone_options` / `ffcb5359`
Patched: `3.1.57` — 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** (CWE-73) exists in GitPython. Attackers reach the vulnerable code path via `GET /internal-metadata` without authentication.
📍 Affected scope
GitPython — . Attack surface: GET /internal-metadata / `transform_kwargs` / `unsafe_git_clone_options` / `ffcb5359`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **3.1.57**.
🛡️ 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 `GET /internal-metadata` requests with malformed payloads or SQL meta-characters. Run `grep -r 'GitPython' .` 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
-
1Identify exposure identify
grep -r 'GitPython' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `GitPython` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'GET /internal-metadata' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `GET /internal-metadata` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade GitPython to 3.1.57ステージング環境で 3.1.57 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against GET /internal-metadata on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
GitPython
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.57"}]}]
References
- web https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-539m-9xh6-q6rr
- web https://github.com/gitpython-developers/GitPython/pull/2193
- web https://github.com/gitpython-developers/GitPython/commit/7a4f5dcb7bf3cbcbf6e438017efcdfe0bc0d36ca
- web https://github.com/gitpython-developers/GitPython/releases/tag/3.1.57
- web https://github.com/advisories/GHSA-539m-9xh6-q6rr