CVE-2011-4137

In Django, CVE-2011-4137 affects the URLField verify_exists check: before 1.2.7 and 1.3.x before 1.3.1, it uses libraries that access arbitrary URLs with no timeout, enabling DoS via slow, data-less, or large-response URLs. Root cause: lack of timeout handling in URL checks. Impact: remote denial...

CVE-2011-4139

CVE-2011-4139 affects Django before 1.2.7 and 1.3.x before 1.3.1. The vulnerability arises when a request’s HTTP Host header is used to construct a full URL in certain circumstances, enabling remote attackers to poison caches via crafted requests. Public data from multiple sources (Ubuntu USN-129...

CVE-2011-4136

CVE-2011-4136 affects Django before 1.2.7 and 1.3.x before 1.3.1, where cached session data uses the root namespace for both session IDs and application data keys. This allows a remote attacker to modify a session by triggering use of a key equal to that session’s identifier. Impact is session in...

CVE-2011-4138

The verifyexists 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 arbitra...

CVE-2011-4139

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...

CVE-2011-4140

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...

CVE-2011-4136

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...

CVE-2011-4137

The verifyexists 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...

PT-2011-4854

Name of the Vulnerable Software and Affected Versions Django versions prior to 1.2.7 Django versions 1.3.x prior to 1.3.1 Description The issue allows remote attackers to modify a session by triggering use of a key that is equal to that session's identifier, when session data is stored in the...

CVE-2011-4140: Cross-Site Request Forgery (CSRF)

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...

CVE-2011-4138: Improper Input Validation

The verifyexists 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 arbitra...

CVE-2011-4136: Improper Input Validation

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...

CVE-2011-4137: Undefined Security Weakness

The verifyexists 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...

CVE-2011-4139: Improper Input Validation

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...

CVE-2011-4136

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...

CVE-2011-4137

The verifyexists 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...

CVE-2011-4138

The verifyexists 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 arbitra...

CVE-2011-4139

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...

PT-2011-4858

Name of the Vulnerable Software and Affected Versions Django versions 1.2.0 through 1.2.7 Django versions 1.3.0 through 1.3.1 Description The issue concerns the CSRF protection mechanism, which does not properly handle web-server configurations that support arbitrary HTTP Host headers. This allow...

PT-2011-4857

Name of the Vulnerable Software and Affected Versions Django versions prior to 1.2.7 Django versions 1.3.x prior to 1.3.1 Description The issue allows remote attackers to conduct cache poisoning attacks by crafting a request that exploits how Django constructs a full URL using a request's HTTP Ho...