← Back
CVE-2009-3695
Vulnerability in django (CVE-2009-3695)
Summary
vulnerability in django (CVE-2009-3695). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `1.0.4, 1.1.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2009-3695** has been found in django.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade django to **1.0.4, 1.1.1** or later.
If unsure, ask your IT team or search "django CVE-2009-3695" on the vendor's site.
CVE-2009-3695 (django) —
Patched: `1.0.4, 1.1.1` — 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 django.
📍 Affected scope
django — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.0.4, 1.1.1**.
🛡️ 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' .` 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' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `django` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade django to 1.0.4, 1.1.1ステージング環境で 1.0.4, 1.1.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
django
[{"type":"ECOSYSTEM","events":[{"introduced":"1.0"},{"fixed":"1.0.4"},{"introduced":"1.1"},{"fixed":"1.1.1"}]}]
References
- advisory http://secunia.com/advisories/36948
- advisory http://www.debian.org/security/2009/dsa-1905
- advisory http://www.vupen.com/english/advisories/2009/2871
- advisory http://secunia.com/advisories/36968
- advisory https://github.com/advisories/GHSA-p6m5-h7pp-v2x5
- web http://www.securityfocus.com/bid/36655
- web http://groups.google.com/group/django-users/browse_thread/thread/15df9e45118dfc51/
- web http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550457
- web http://www.djangoproject.com/weblog/2009/oct/09/security/
- web http://www.openwall.com/lists/oss-security/2009/10/13/6
- web https://exchange.xforce.ibmcloud.com/vulnerabilities/53727