← Back
CVE-2024-29905
Vulnerability in dirac (CVE-2024-29905)
Summary
vulnerability in dirac (CVE-2024-29905). Confidential information can be exposed externally. Exploitable via ``X509_USER_PROXY``. Mitigation: upgrade to `8.0.41` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-29905** has been found in dirac.
Attackers can target a specific entry point like ``X509_USER_PROXY`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade dirac to **8.0.41** or later.
If unsure, ask your IT team or search "dirac CVE-2024-29905" on the vendor's site.
CVE-2024-29905 (dirac) — CWE-668 /
Attack vector: local
Attack surface: `X509_USER_PROXY`
Patched: `8.0.41` — apply immediately
Workaround: Setting the `X509_USER_PROXY` environment variable to a path that is inside a directory that is only readable to the current user avoids the potential risk.
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-668) exists in dirac. Attackers reach the vulnerable code path via ``X509_USER_PROXY`` without authentication.
📍 Affected scope
dirac — . Attack surface: `X509_USER_PROXY`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **8.0.41**.
🛡️ Workaround
Workaround: Setting the `X509_USER_PROXY` environment variable to a path that is inside a directory that is only readable to the current user avoids the potential risk.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'dirac' .` 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 'dirac' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `dirac` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Setting the `X509_USER_PROXY` environment variable to a path that is inside a directory that is only readable to the current user avoids the potential risk.パッチが適用されるまでの応急処置として、Setting the `X509_USER_PROXY` environment variable to a path that is inside a directory that is only readable to the current user avoids the potential risk. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade dirac to 8.0.41ステージング環境で 8.0.41 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
dirac
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.0.41"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-29905
- advisory https://github.com/advisories/GHSA-v6f3-gh5h-mqwx
- package https://github.com/DIRACGrid/DIRAC
- package https://pypi.org/project/dirac
- web https://github.com/DIRACGrid/DIRAC/security/advisories/GHSA-v6f3-gh5h-mqwx
- web https://github.com/DIRACGrid/DIRAC/commit/1faa709341969a6321e29c843ca94039d33b2c3d