← Back
UBUNTU-CVE-2023-41040
Vulnerability in python-git (UBUNTU-CVE-2023-41040)
Summary
vulnerability in python-git (UBUNTU-CVE-2023-41040). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `0.3.2~RC1-3ubuntu0.1~esm3` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **UBUNTU-CVE-2023-41040** has been found in python-git.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade python-git to **0.3.2~RC1-3ubuntu0.1~esm3** or later.
If unsure, ask your IT team or search "python-git UBUNTU-CVE-2023-41040" on the vendor's site.
UBUNTU-CVE-2023-41040 (python-git) —
Attack vector: local / unauthenticated / no user interaction
Patched: `0.3.2~RC1-3ubuntu0.1~esm3` — 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 python-git.
📍 Affected scope
python-git — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.3.2~RC1-3ubuntu0.1~esm3**.
🛡️ 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 'python-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
-
1Identify exposure identify
grep -r 'python-git' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `python-git` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade python-git to 0.3.2~RC1-3ubuntu0.1~esm3ステージング環境で 0.3.2~RC1-3ubuntu0.1~esm3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Ubuntu:Pro:14.04:LTS
python-git
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.3.2~RC1-3ubuntu0.1~esm3"}]}]
Ubuntu:Pro:16.04:LTS
python-git
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.0.1+git137-gc8b8379-2.1ubuntu0.1~esm4"}]}]
Ubuntu:Pro:18.04:LTS
python-git
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.1.8-1ubuntu0.1~esm4"}]}]
Ubuntu:Pro:20.04:LTS
python-git
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.7-1ubuntu0.1~esm4"}]}]
Ubuntu:Pro:22.04:LTS
python-git
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.24-1ubuntu0.1~esm3"}]}]
Ubuntu:24.04:LTS
python-git
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:25.10
python-git
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:26.04:LTS
python-git
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
References
- advisory https://ubuntu.com/security/notices/USN-8303-1
- report https://ubuntu.com/security/CVE-2023-41040
- report https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-cwvm-v4w8-q58c
- report https://github.com/gitpython-developers/GitPython/blob/1c8310d7cae144f74a671cbe17e51f63a830adbf/git/refs/symbolic.py#L174-L175
- report https://www.cve.org/CVERecord?id=CVE-2023-41040