← Back
GHSA-r3hx-x5rh-p9vv
Vulnerability in django-haystack (GHSA-r3hx-x5rh-p9vv)
Summary
vulnerability in django-haystack (GHSA-r3hx-x5rh-p9vv). Risk of unauthorized operations or information disclosure. Exploitable via ``SearchField``. Mitigation: upgrade to `3.4.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-r3hx-x5rh-p9vv** has been found in django-haystack.
Attackers can target a specific entry point like ``SearchField`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade django-haystack to **3.4.0** or later.
If unsure, ask your IT team or search "django-haystack GHSA-r3hx-x5rh-p9vv" on the vendor's site.
GHSA-r3hx-x5rh-p9vv (django-haystack) — CWE-95 /
Attack surface: `SearchField` / `index_fieldname` / `index.fields` / `final_data`
Patched: `3.4.0` — 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-95) exists in django-haystack. Attackers reach the vulnerable code path via ``SearchField`` without authentication.
📍 Affected scope
django-haystack — . Attack surface: `SearchField` / `index_fieldname` / `index.fields` / `final_data`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **3.4.0**.
🛡️ 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 'django-haystack' .` 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 'django-haystack' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `django-haystack` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade django-haystack to 3.4.0ステージング環境で 3.4.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
django-haystack
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.4.0"}]}]
References
- web https://github.com/django-haystack/django-haystack/security/advisories/GHSA-r3hx-x5rh-p9vv
- web https://github.com/django-haystack/django-haystack/commit/eb05f193c9771a68dcc8cfac6674a0d48a52ee9d
- web https://github.com/django-haystack/django-haystack/releases/tag/v3.4.0
- web https://github.com/advisories/GHSA-r3hx-x5rh-p9vv