Vulnerabilities > Djangoproject > Django

DATE CVE VULNERABILITY TITLE RISK
2012-07-31 CVE-2012-3442 Cross-Site Scripting vulnerability in Djangoproject Django
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.
4.3
2011-10-19 CVE-2011-4140 Cross-Site Request Forgery (CSRF) vulnerability in Djangoproject Django
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 arbitrary HTTP Host headers, which allows remote attackers to trigger unauthenticated forged requests via vectors involving a DNS CNAME record and a web page containing JavaScript code.
6.8
2011-10-19 CVE-2011-4139 Improper Input Validation vulnerability in Djangoproject Django
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 remote attackers to conduct cache poisoning attacks via a crafted request.
network
low complexity
djangoproject CWE-20
5.0
2011-10-19 CVE-2011-4138 Improper Input Validation vulnerability in Djangoproject Django
The verify_exists functionality in the URLField implementation in Django before 1.2.7 and 1.3.x before 1.3.1 originally tests a URL's validity through a HEAD request, but then uses a GET request for the new target URL in the case of a redirect, which might allow remote attackers to trigger arbitrary GET requests with an unintended source IP address via a crafted Location header.
network
low complexity
djangoproject CWE-20
5.0
2011-10-19 CVE-2011-4137 Resource Management Errors vulnerability in Djangoproject Django
The verify_exists functionality in the URLField implementation in Django before 1.2.7 and 1.3.x before 1.3.1 relies on Python libraries that attempt access to an arbitrary URL with no timeout, which allows remote attackers to cause a denial of service (resource consumption) via a URL associated with (1) a slow response, (2) a completed TCP connection with no application data sent, or (3) a large amount of application data, a related issue to CVE-2011-1521.
network
low complexity
djangoproject CWE-399
5.0
2011-10-19 CVE-2011-4136 Improper Input Validation vulnerability in Djangoproject Django
django.contrib.sessions in Django before 1.2.7 and 1.3.x before 1.3.1, when session data is stored in the cache, uses the root namespace for both session identifiers and application-data keys, which allows remote attackers to modify a session by triggering use of a key that is equal to that session's identifier.
5.8
2011-02-14 CVE-2011-0698 Path Traversal vulnerability in Djangoproject Django
Directory traversal vulnerability in Django 1.1.x before 1.1.4 and 1.2.x before 1.2.5 on Windows might allow remote attackers to read or execute files via a / (slash) character in a key in a session cookie, related to session replays.
network
low complexity
djangoproject microsoft CWE-22
7.5
2011-02-14 CVE-2011-0697 Cross-Site Scripting vulnerability in Djangoproject Django
Cross-site scripting (XSS) vulnerability in Django 1.1.x before 1.1.4 and 1.2.x before 1.2.5 might allow remote attackers to inject arbitrary web script or HTML via a filename associated with a file upload.
4.3
2011-02-14 CVE-2011-0696 Cross-Site Request Forgery (CSRF) vulnerability in Djangoproject Django
Django 1.1.x before 1.1.4 and 1.2.x before 1.2.5 does not properly validate HTTP requests that contain an X-Requested-With header, which makes it easier for remote attackers to conduct cross-site request forgery (CSRF) attacks via forged AJAX requests that leverage a "combination of browser plugins and redirects," a related issue to CVE-2011-0447.
6.8
2011-01-10 CVE-2010-4535 Improper Input Validation vulnerability in Djangoproject Django
The password reset functionality in django.contrib.auth in Django before 1.1.3, 1.2.x before 1.2.4, and 1.3.x before 1.3 beta 1 does not validate the length of a string representing a base36 timestamp, which allows remote attackers to cause a denial of service (resource consumption) via a URL that specifies a large base36 integer.
network
low complexity
djangoproject CWE-20
5.0