Skip to content
Noroxi
NVD / CVE Program· CNA redhat

CVE-2012-3442: The (1) django.http.HttpResponseRedirect and (2) django.http.HttpResponsePermanentRedirect classes in Django before 1.3.2 and 1.4.x before…

MediumCVSS 4.3 · v2.0—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 18/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 2% (FIRST EPSS); higher than 81.6% of all records.
  • Fixed version: python-django (Debian:12) 1.4.1-1; python-django (Debian:6.0) 1.2.3-3+squeeze3; django (PyPI) 1.4.1, 1.3.2.

Low priority for now. Upgrade to python-django (Debian:12) 1.4.1-1; python-django (Debian:6.0) 1.2.3-3+squeeze3; django (PyPI) 1.4.1, 1.3.2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Jul 31, 2012
Updated
Jun 16, 2026
EPSS
2.0% · 81th percentile

Report tools

JSON

Action score

18

Monitor

Low priority for now.

CVSS
17 / 40 · 4.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.0%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2012-3442

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Limit the impact of XSSCheck security headers

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Limit the impact of XSSCheck security headers

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
djangoprojectdjango

Limit the impact of XSS

This is a cross-site scripting (XSS) vulnerability. A well-configured Content-Security-Policy doesn't fix it, but greatly reduces its impact. Check your site's CSP and other security headers for free.

Check security headers

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • djangoproject djangobefore 1.3.2
  • djangoproject django1.4

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12python-djangobefore 1.4.1-11.4.1-1
Debian:6.0python-djangobefore 1.2.3-3+squeeze31.2.3-3+squeeze3
PyPIdjangofrom 1.4 · before 1.4.11.4.1
PyPIdjangobefore 1.3.21.3.2

Other highest-scoring records for the same primary product.

  • CVE-2022-34265An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6.
    61This week
  • CVE-2020-7471Django 1.11 before 1.11.28, 2.2 before 2.2.10, and 3.0 before 3.0.3 allows SQL Injection if untrusted data is used as a StringAgg delimiter…
    59Plan
  • CVE-2019-19844Django before 1.11.27, 2.x before 2.2.9, and 3.x before 3.0.1 allows account takeover.
    55Plan

Published before and after this one in the same product

  • ← EarlierCVE-2011-4139Oct 19, 2011 · Django before 1.2.7 and 1.3.x before 1.3.1 uses a request's HTTP Host header to construct a full URL in certain circumstances, which allows…
    21Monitor
  • ← EarlierCVE-2011-4140Oct 19, 2011 · The CSRF protection mechanism in Django through 1.2.7 and 1.3.x through 1.3.1 does not properly handle web-server configurations supporting…
    27Monitor
  • Later →CVE-2012-3443Jul 31, 2012 · The django.forms.ImageField class in the form system in Django before 1.3.2 and 1.4.x before 1.4.1 completely decompresses image data…
    21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:python-django1.4.1-1 · Debian:12Package registry (OSV)
PyPI:django1.3.2Package registry (OSV)
PyPI:django1.4.1Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

    If successful

    Confidentiality
    none
    Integrity
    P · data or configuration can be modified
    Availability
    none
    Attack complexity
    M
    Confidentiality impact
    None
    Integrity impact
    P
    Availability impact
    None

    CVSS vector

    AV:N/AC:M/Au:N/C:N/I:P/A:N

    nvd-primary

    Root cause

    User content is inserted into the page as HTML. The browser interprets the content as code rather than data.

    A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

    Vulnerable

    ts
    commentEl.innerHTML = comment.body;

    Fixed

    ts
    commentEl.textContent = comment.body;

    References

    All records