
26/8/2014

14/5/2022

18/9/2024
CVE-2014-0480: Input Validation
First published: Tue Aug 26 2014(Updated: )
The `core.urlresolvers.reverse` function in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 does not properly validate URLs, which allows remote attackers to conduct phishing attacks via a `//` (slash slash) in a URL, which triggers a scheme-relative URL to be generated.
Credit: security@debian.org security@debian.org
Affected Software | Affected Version | How to fix |
---|
pip/Django | >=1.6<1.6.6 | 1.6.6 |
pip/Django | >=1.5<1.5.9 | 1.5.9 |
pip/django | <1.4.14 | 1.4.14 |
openSUSE | =12.3 | |
openSUSE | =13.1 | |
djangoproject Django | =1.7-beta1 | |
djangoproject Django | =1.7-beta2 | |
djangoproject Django | =1.7-beta3 | |
djangoproject Django | =1.7-beta4 | |
djangoproject Django | =1.7-rc1 | |
djangoproject Django | =1.7-rc2 | |
djangoproject Django | =1.6 | |
djangoproject Django | =1.6-beta1 | |
djangoproject Django | =1.6-beta2 | |
djangoproject Django | =1.6-beta3 | |
djangoproject Django | =1.6-beta4 | |
djangoproject Django | =1.6.1 | |
djangoproject Django | =1.6.2 | |
djangoproject Django | =1.6.3 | |
djangoproject Django | =1.6.4 | |
djangoproject Django | =1.6.5 | |
djangoproject Django | =1.5 | |
djangoproject Django | =1.5-alpha | |
djangoproject Django | =1.5-beta | |
djangoproject Django | =1.5.1 | |
djangoproject Django | =1.5.2 | |
djangoproject Django | =1.5.3 | |
djangoproject Django | =1.5.4 | |
djangoproject Django | =1.5.5 | |
djangoproject Django | =1.5.6 | |
djangoproject Django | =1.5.7 | |
djangoproject Django | =1.5.8 | |
djangoproject Django | <=1.4.13 | |
djangoproject Django | =1.4 | |
djangoproject Django | =1.4.1 | |
djangoproject Django | =1.4.2 | |
djangoproject Django | =1.4.4 | |
djangoproject Django | =1.4.5 | |
djangoproject Django | =1.4.6 | |
djangoproject Django | =1.4.7 | |
djangoproject Django | =1.4.8 | |
djangoproject Django | =1.4.9 | |
djangoproject Django | =1.4.10 | |
djangoproject Django | =1.4.11 | |
djangoproject Django | =1.4.12 | |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the severity of CVE-2014-0480?
CVE-2014-0480 is classified as a high severity vulnerability that allows for phishing attacks due to improper URL validation in Django.
How do I fix CVE-2014-0480?
To fix CVE-2014-0480, upgrade Django to versions 1.4.14, 1.5.9, 1.6.6 or newer.
What versions of Django are affected by CVE-2014-0480?
CVE-2014-0480 affects Django versions before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3.
Can I continue using Django if it has CVE-2014-0480?
It is highly discouraged to continue using Django with CVE-2014-0480 as it exposes your application to phishing risks.
What functions are affected by CVE-2014-0480?
The `core.urlresolvers.reverse` function is affected by CVE-2014-0480, which improperly validates URLs.
- agent/author
- agent/type
- agent/weakness
- agent/remedy
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/first-publish-date
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-f7cm-ccfp-3q4r
- alias/CVE-2014-0480
- agent/software-canonical-lookup
- agent/last-modified-date
- agent/severity
- agent/references
- agent/event
- collector/github-advisory
- agent/softwarecombine
- agent/trending
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- collector/nvd-cve
- source/NVD
- package-manager/pip
- vendor/opensuse
- canonical/opensuse
- version/opensuse/12.3
- version/opensuse/13.1
- vendor/djangoproject
- canonical/djangoproject django
- version/djangoproject django/1.7-beta1
- version/djangoproject django/1.7-beta2
- version/djangoproject django/1.7-beta3
- version/djangoproject django/1.7-beta4
- version/djangoproject django/1.7-rc1
- version/djangoproject django/1.7-rc2
- version/djangoproject django/1.6
- version/djangoproject django/1.6-beta1
- version/djangoproject django/1.6-beta2
- version/djangoproject django/1.6-beta3
- version/djangoproject django/1.6-beta4
- version/djangoproject django/1.6.1
- version/djangoproject django/1.6.2
- version/djangoproject django/1.6.3
- version/djangoproject django/1.6.4
- version/djangoproject django/1.6.5
- version/djangoproject django/1.5
- version/djangoproject django/1.5-alpha
- version/djangoproject django/1.5-beta
- version/djangoproject django/1.5.1
- version/djangoproject django/1.5.2
- version/djangoproject django/1.5.3
- version/djangoproject django/1.5.4
- version/djangoproject django/1.5.5
- version/djangoproject django/1.5.6
- version/djangoproject django/1.5.7
- version/djangoproject django/1.5.8
- version/djangoproject django/1.4.13
- version/djangoproject django/1.4
- version/djangoproject django/1.4.1
- version/djangoproject django/1.4.2
- version/djangoproject django/1.4.4
- version/djangoproject django/1.4.5
- version/djangoproject django/1.4.6
- version/djangoproject django/1.4.7
- version/djangoproject django/1.4.8
- version/djangoproject django/1.4.9
- version/djangoproject django/1.4.10
- version/djangoproject django/1.4.11
- version/djangoproject django/1.4.12
Contact
SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.coBy using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203