CVE-2012-3442
Django Allows Redirect via Data URL
The (1) django.http.HttpResponseRedirect and (2) django.http.HttpResponsePermanentRedirect classes in Django before 1.3.2 and 1.4.x before 1.4.1 do not validate the scheme of a redirect target, which might allow remote attackers to conduct cross-site scripting (XSS) attacks via a data: URL.
Exploit likelihood
What each source reports
NVD Score used
The (1) django.http.HttpResponseRedirect and (2) django.http.HttpResponsePermanentRedirect classes in Django before 1.3.2 and 1.4.x before 1.4.1 do not validate the scheme of a redirect target, which might allow remote attackers to conduct cross-site scripting (XSS) attacks via a data: URL.
- Record
CVE-2012-3442- CVSS 2.0
- 4.3 Medium
AV:N/AC:M/Au:N/C:N/I:P/A:N - Weakness
- CWE-79
- Updated
- 2026-11-02
CVE List No score
The (1) django.http.HttpResponseRedirect and (2) django.http.HttpResponsePermanentRedirect classes in Django before 1.3.2 and 1.4.x before 1.4.1 do not validate the scheme of a redirect target, which might allow remote attackers to conduct cross-site scripting (XSS) attacks via a data: URL.
- Record
CVE-2012-3442- Updated
- 2026-11-02
EUVDEUVD-2012-0003 No score
The (1) django.http.HttpResponseRedirect and (2) django.http.HttpResponsePermanentRedirect classes in Django before 1.3.2 and 1.4.x before 1.4.1 do not validate the scheme of a redirect target, which might allow remote attackers to conduct cross-site scripting (XSS) attacks via a data: URL.
- Record
EUVD-2012-0003- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-78vx-ggch-wghm
Django Allows Redirect via Data URL
The (1) django.http.HttpResponseRedirect and (2) django.http.HttpResponsePermanentRedirect classes in Django before 1.3.2 and 1.4.x before 1.4.1 do not validate the scheme of a redirect target, which might allow remote attackers to conduct cross-site scripting (XSS) attacks via a data: URL.
- Record
GHSA-78vx-ggch-wghm- CVSS 4.0
- 9.3 Critical
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N - CVSS 3.1
- 6.1 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N - Weakness
- CWE-79
- Updated
- 2026-11-02
OSVGHSA-78vx-ggch-wghm
Django Allows Redirect via Data URL
The (1) django.http.HttpResponseRedirect and (2) django.http.HttpResponsePermanentRedirect classes in Django before 1.3.2 and 1.4.x before 1.4.1 do not validate the scheme of a redirect target, which might allow remote attackers to conduct cross-site scripting (XSS) attacks via a data: URL.
- Record
GHSA-78vx-ggch-wghm- CVSS 4.0
- 9.3 Critical
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N - CVSS 3.1
- 6.1 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N - Weakness
- CWE-79
- Updated
- 2026-11-02
OSV No score
The (1) django.http.HttpResponseRedirect and (2) django.http.HttpResponsePermanentRedirect classes in Django before 1.3.2 and 1.4.x before 1.4.1 do not validate the scheme of a redirect target, which might allow remote attackers to conduct cross-site scripting (XSS) attacks via a data: URL.
- Record
CVE-2012-3442- Updated
- 2026-11-02
OSVDEBIAN-CVE-2012-3442 No score
The (1) django.http.HttpResponseRedirect and (2) django.http.HttpResponsePermanentRedirect classes in Django before 1.3.2 and 1.4.x before 1.4.1 do not validate the scheme of a redirect target, which might allow remote attackers to conduct cross-site scripting (XSS) attacks via a data: URL.
- Record
DEBIAN-CVE-2012-3442- Updated
- 2026-11-02
OSVPYSEC-2012-2 No score
The (1) django.http.HttpResponseRedirect and (2) django.http.HttpResponsePermanentRedirect classes in Django before 1.3.2 and 1.4.x before 1.4.1 do not validate the scheme of a redirect target, which might allow remote attackers to conduct cross-site scripting (XSS) attacks via a data: URL.
- Record
PYSEC-2012-2- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
djangoPyPI |
before 1.3.2 | 1.3.2 |
djangoPyPI |
1.4 up to 1.4.1 | 1.4.1 |
python-djangoDebian:12 |
before 1.4.1-1 | 1.4.1-1 |
python-djangoDebian:13 |
before 1.4.1-1 | 1.4.1-1 |
python-djangoDebian:14 |
before 1.4.1-1 | 1.4.1-1 |
python-djangoDebian:6.0 From an advisory covering 3 CVEs |
before 1.2.3-3+squeeze3, plus listed versions 1.2.3-31.2.3-3+squeeze11.2.3-3+squeeze2 |
1.2.3-3+squeeze3 |
djangoPyPI |
before 1.3.2, plus listed versions 1.0.11.0.21.0.31.0.41.1 Show 14 moreShow less1.1.11.1.21.1.31.1.41.21.2.11.2.21.2.31.2.41.2.51.2.61.2.71.31.3.1 |
1.3.2 |
djangoPyPI |
before 1.3.2, 1.4 up to 1.4.1, plus listed versions 1.0.11.0.21.0.31.0.41.1 Show 14 moreShow less1.1.11.1.21.1.31.1.41.21.2.11.2.21.2.31.2.41.2.51.2.61.2.71.31.3.1 |
1.3.21.4.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, facts | ||
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2012-3442 is a medium vulnerability (CVSS 4.3) in Djangoproject Django, published July 31, 2012. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 2.06%, the 81st percentile. Fixed in django 1.3.2.
References
openwall.com/lists/oss-security/2012/07/31/1
djangoproject.com/weblog/2012/jul/30/security-releases-issued
mandriva.com/security/advisories?name=MDVSA-2012:143
ubuntu.com/usn/USN-1560-1
debian.org/security/2012/dsa-2529
Show 7 moreShow less
nvd.nist.gov/vuln/detail/CVE-2012-3442
github.com/django/django/commit/4dea4883e6c50d75f215a6b9bcbd95273f57c72d
security-tracker.debian.org/tracker/CVE-2012-3442