CVE-2012-3442 json
Django Allows Redirect via Data URL
published 2012-07-31 14 y ago modified 2026-06-16 4 mo ago also GHSA-78vx-ggch-wghm , PYSEC-2012-2 , EUVD-2012-0003
- cvss
- 6.1
- version 3.1, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.1%
- EPSS 2.1% chance of exploitation in 30 days, percentile 81%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- pypi django 1.3.2, 1.4.1
- djangoproject django 1.3.2
- python-django Debian 14, Debian 13, Debian 12 1.4.1-1
debian advisories DEBIAN-CVE-2012-3442
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2012-3442 updated cvss 4.3
Django: 1.3.1 and 1.4.0 Cross-site scripting in authentication views
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
2.06% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
| GitHub | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | django | <1.3.2 >=1.4, <1.4.1 |
1.3.2 1.4.1 |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
-
djangoproject.com
/weblog/2012/jul/30/security-releases-issued/
patch, vendor-advisory, article
-
github.com
/django/django/commit/4dea4883e6c50d75f215a6b9bcbd95273f57c72d
web
-
github.com
/django/django/commit/e34685034b60be1112160e76091e5aee60149fa1
web
-
mandriva.com
/security/advisories?name=MDVSA-2012:143
vendor-advisory, web, broken-link, advisory
-
ubuntu.com
/usn/USN-1560-1
vendor-advisory, web, broken-link, advisory
-
debian.org
/security/2012/dsa-2529
vendor-advisory, web, third-party-advisory, advisory
-
openwall.com
/lists/oss-security/2012/07/31/1
mailing-list, web, third-party-advisory
-
openwall.com
/lists/oss-security/2012/07/31/2
mailing-list, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2012-3442
advisory
-
github.com
/django/django
package
-
github.com
/pypa/advisory-database/tree/main/vulns/django/PYSEC-2012-2.yaml
web
-
djangoproject.com
/weblog/2012/jul/30/security-releases-issued
web
-
github.com
/advisories/GHSA-78vx-ggch-wghm
advisory
Sources
- CVE List CVE-2012-3442
- GitHub Advisory GHSA-78vx-ggch-wghm
- NVD CVE-2012-3442
- OSV PYSEC-2012-2
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.