Skip to content
Noroxi
NVD / CVE Program· CNA debian

CVE-2014-3730: The django.util.http.is_safe_url function in Django 1.4 before 1.4.13, 1.5 before 1.5.8, 1.6 before 1.6.5, and 1.7 before 1.7b4 does not…

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: 3.1% (FIRST EPSS); higher than 88.1% of all records.
  • Fixed version: python-django (Debian:12) 1.6.5-1; python-django (Debian:6.0) 1.2.3-3+squeeze10; python-django (Debian:7) 1.4.5-1+deb7u7.

Low priority for now. Upgrade to python-django (Debian:12) 1.6.5-1; python-django (Debian:6.0) 1.2.3-3+squeeze10; python-django (Debian:7) 1.4.5-1+deb7u7 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 django.util.http.is_safe_url function in Django 1.4 before 1.4.13, 1.5 before 1.5.8, 1.6 before 1.6.5, and 1.7 before 1.7b4 does not properly validate URLs, which allows remote attackers to conduct open redirect attacks via a malformed URL, as demonstrated by "http:\\\djangoproject.com."

Published
May 16, 2014
Updated
Jun 16, 2026
EPSS
3.1% · 88th 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 · 3.1%

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-2014-3730

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.

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
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
canonicalubuntu linux
djangoprojectdjango
opensuseopensuse
debiandebian linux

Affected versions

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

  • canonical ubuntu linux10.04
  • canonical ubuntu linux12.04
  • canonical ubuntu linux12.10
  • canonical ubuntu linux13.10
  • canonical ubuntu linux14.04
  • debian debian linux7.0
  • debian debian linux8.0
  • 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.6.5-11.6.5-1
Debian:6.0python-djangobefore 1.2.3-3+squeeze101.2.3-3+squeeze10
Debian:7python-djangobefore 1.4.5-1+deb7u71.4.5-1+deb7u7
PyPIdjangofrom 1.4 · before 1.4.131.4.13
PyPIdjangofrom 1.5 · before 1.5.81.5.8
PyPIdjangofrom 1.6 · before 1.6.51.6.5
PyPIdjangofrom 1.7a0 · before 1.7b41.7b4
PyPIdjangofrom 1.7a1 · before 1.7b41.7b4

Other highest-scoring records for the same primary product.

  • CVE-2021-3493The overlayfs implementation in the linux kernel did not properly validate with respect to user namespaces the setting of file capabilities…KEV
    76This week
  • CVE-2017-14492Heap-based buffer overflow in dnsmasq before 2.78 allows remote attackers to cause a denial of service (crash) or execute arbitrary code…
    67This week
  • CVE-2017-14493Stack-based buffer overflow in dnsmasq before 2.78 allows remote attackers to cause a denial of service (crash) or execute arbitrary code…
    65This week

Published before and after this one in the same product

  • ← EarlierCVE-2014-0474Apr 23, 2014 · The (1) FilePathField, (2) GenericIPAddressField, and (3) IPAddressField model field classes in Django before 1.4.11, 1.5.x before 1.5.6, 1.
    41Plan
  • ← EarlierCVE-2013-7374May 1, 2014 · The Ubuntu Date and Time Indicator (aka indicator-datetime) 13.10.0+13.10.x before 13.10.0+13.10.20131023.2-0ubuntu1.1 does not properly…
    18Monitor
  • Later →CVE-2014-3925Jun 1, 2014 · sosreport in Red Hat sos 1.7 and earlier on Red Hat Enterprise Linux (RHEL) 5 produces an archive with an fstab file potentially containing…
    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.6.5-1 · Debian:12Package registry (OSV)
PyPI:django1.4.13Package registry (OSV)
PyPI:django1.5.8Package registry (OSV)
PyPI:django1.6.5Package registry (OSV)
PyPI:django1.7b4Package 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

References

All records