Vulnerabilities > Djangoproject > Django > Medium
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2013-05-02 | CVE-2013-0305 | Information Exposure vulnerability in multiple products The administrative interface for Django 1.3.x before 1.3.6, 1.4.x before 1.4.4, and 1.5 before release candidate 2 does not check permissions for the history view, which allows remote authenticated administrators to obtain sensitive object history information. | 4.0 |
| 2012-11-18 | CVE-2012-4520 | Improper Input Validation vulnerability in Djangoproject Django The django.http.HttpRequest.get_host function in Django 1.3.x before 1.3.4 and 1.4.x before 1.4.2 allows remote attackers to generate and display arbitrary URLs via crafted username and password Host header values. | 6.4 |
| 2012-07-31 | CVE-2012-3444 | Improper Restriction of Operations Within the Bounds of A Memory Buffer vulnerability in Djangoproject Django The get_image_dimensions function in the image-handling functionality in Django before 1.3.2 and 1.4.x before 1.4.1 uses a constant chunk size in all attempts to determine dimensions, which allows remote attackers to cause a denial of service (process or thread consumption) via a large TIFF image. | 5.0 |
| 2012-07-31 | CVE-2012-3443 | Improper Input Validation vulnerability in Djangoproject Django 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 during image validation, which allows remote attackers to cause a denial of service (memory consumption) by uploading an image file. | 5.0 |
| 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. | 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. | 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. | 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 |