Show filters
16 Total Results
Displaying 11-16 of 16
Sort by:
Attacker Value
Unknown
CVE-2015-5143
Disclosure Date: July 14, 2015 (last updated October 05, 2023)
The session backends in Django before 1.4.21, 1.5.x through 1.6.x, 1.7.x before 1.7.9, and 1.8.x before 1.8.3 allows remote attackers to cause a denial of service (session store consumption) via multiple requests with unique session keys.
0
Attacker Value
Unknown
CVE-2015-5145
Disclosure Date: July 14, 2015 (last updated October 05, 2023)
validators.URLValidator in Django 1.8.x before 1.8.3 allows remote attackers to cause a denial of service (CPU consumption) via unspecified vectors.
0
Attacker Value
Unknown
CVE-2015-3982
Disclosure Date: June 02, 2015 (last updated October 05, 2023)
The session.flush function in the cached_db backend in Django 1.8.x before 1.8.2 does not properly flush the session, which allows remote attackers to hijack user sessions via an empty string in the session key.
0
Attacker Value
Unknown
CVE-2015-2317
Disclosure Date: March 25, 2015 (last updated October 05, 2023)
The utils.http.is_safe_url function in Django before 1.4.20, 1.5.x, 1.6.x before 1.6.11, 1.7.x before 1.7.7, and 1.8.x before 1.8c1 does not properly validate URLs, which allows remote attackers to conduct cross-site scripting (XSS) attacks via a control character in a URL, as demonstrated by a \x08javascript: URL.
0
Attacker Value
Unknown
CVE-2015-2316
Disclosure Date: March 25, 2015 (last updated October 05, 2023)
The utils.html.strip_tags function in Django 1.6.x before 1.6.11, 1.7.x before 1.7.7, and 1.8.x before 1.8c1, when using certain versions of Python, allows remote attackers to cause a denial of service (infinite loop) by increasing the length of the input string.
0
Attacker Value
Unknown
CVE-2015-2241
Disclosure Date: March 12, 2015 (last updated October 05, 2023)
Cross-site scripting (XSS) vulnerability in the contents function in admin/helpers.py in Django before 1.7.6 and 1.8 before 1.8b2 allows remote attackers to inject arbitrary web script or HTML via a model attribute in ModelAdmin.readonly_fields, as demonstrated by a @property.
0