← Back
CVE-2010-4535
Vulnerability in django (CVE-2010-4535)
Summary
vulnerability in django (CVE-2010-4535). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `1.2.4` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2010-4535** has been found in django.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade django to **1.2.4** or later.
If unsure, ask your IT team or search "django CVE-2010-4535" on the vendor's site.
CVE-2010-4535 (django) — CWE-20 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `1.2.4` — 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-20) exists in django.
📍 Affected scope
django — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.2.4**.
🛡️ 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.2.4ステージング環境で 1.2.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
django
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.2.4"}]}]
PyPI
django
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.3"},{"introduced":"1.2"},{"fixed":"1.2.4"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2010-4535
- advisory https://github.com/advisories/GHSA-7wph-fc4w-wqp2
- advisory http://www.ubuntu.com/usn/USN-1040-1
- advisory http://secunia.com/advisories/42715
- advisory http://secunia.com/advisories/42827
- advisory http://secunia.com/advisories/42913
- advisory http://www.vupen.com/english/advisories/2011/0048
- advisory http://www.vupen.com/english/advisories/2011/0098
- package https://github.com/django/django
- patch https://bugzilla.redhat.com/show_bug.cgi?id=665373
- patch http://code.djangoproject.com/changeset/15032
- patch http://www.openwall.com/lists/oss-security/2010/12/23/4
- patch http://www.openwall.com/lists/oss-security/2011/01/03/5
- patch http://www.djangoproject.com/weblog/2010/dec/22/security/
- web http://lists.fedoraproject.org/pipermail/package-announce/2011-January/053041.html
- web http://lists.fedoraproject.org/pipermail/package-announce/2011-January/053072.html
- web https://github.com/django/django/commit/7f8dd9cbac074389af8d8fd235bf2cb657227b9a
- web https://github.com/django/django/commit/d5d8942a160685c403d381a279e72e09de5489a9
- web http://www.djangoproject.com/weblog/2010/dec/22/security
- web https://github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2011-9.yaml
- web https://web.archive.org/web/20200228193349/http://www.securityfocus.com/bid/45563
- web https://github.com/pypa/advisory-database/tree/main/vulns/django/PYSEC-2011-29.yaml
- web http://www.securityfocus.com/bid/45563