← Back
CVE-2024-41950
Vulnerability in haystack-ai (CVE-2024-41950)
Summary
vulnerability in haystack-ai (CVE-2024-41950). Successful exploitation can lead to full system takeover. Mitigation: upgrade to `2.3.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-41950** has been found in haystack-ai.
Successful exploitation can lead to full system takeover. CVSS score: ?/10.
What to do: upgrade haystack-ai to **2.3.1** or later.
If unsure, ask your IT team or search "haystack-ai CVE-2024-41950" on the vendor's site.
CVE-2024-41950 (haystack-ai) — CWE-1336 /
Attack vector: remote (network-reachable) / no user interaction
Patched: `2.3.1` — apply immediately
Workaround: Prevent users from running the affected Components, or only let users use preselected templates.
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-1336) exists in haystack-ai.
📍 Affected scope
haystack-ai — .
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **2.3.1**.
🛡️ Workaround
Workaround: Prevent users from running the affected Components, or only let users use preselected templates.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'haystack-ai' .` 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 'haystack-ai' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `haystack-ai` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Prevent users from running the affected Components, or only let users use preselected templates.パッチが適用されるまでの応急処置として、Prevent users from running the affected Components, or only let users use preselected templates. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade haystack-ai to 2.3.1ステージング環境で 2.3.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
haystack-ai
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.3.1"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-41950
- advisory https://github.com/advisories/GHSA-hx9v-6r9f-w677
- package https://github.com/deepset-ai/haystack
- package https://pypi.org/project/haystack-ai
- web https://github.com/deepset-ai/haystack/security/advisories/GHSA-hx9v-6r9f-w677
- web https://github.com/deepset-ai/haystack/pull/8095
- web https://github.com/deepset-ai/haystack/pull/8096
- web https://github.com/deepset-ai/haystack/commit/3fed1366c448b02189851bf08166c1f6477a02b0
- web https://github.com/deepset-ai/haystack/commit/6c25a5c73e83aa32c3241ba84a5cbb3ac0e8a89e
- web https://github.com/deepset-ai/haystack/releases/tag/v2.3.1