CVE-2015-5963: High severity django vulnerability
contrib.sessions.middleware.SessionMiddleware in Django 1.8.x before 1.8.4, 1.7.x before 1.7.10, 1.4.x before 1.4.22, and possibly other versions allows remote attackers to cause a denial of service (session store consumption or session record removal) via a large number of requests to contrib.auth.views.logout, which triggers the creation of an empty session record.
Other sources
contrib.sessions.middleware.SessionMiddleware in Django 1.8.x before 1.8.4, 1.7.x before 1.7.10, 1.4.x before 1.4.22, and possibly other versions allows remote attackers to cause a denial of service (session store consumption or session record removal) via a large number of requests to contrib.auth.views.logout, which triggers the creation of an empty session record.
— MITRE
Following issue was reported in Django:
Previously, a session could be created when anonymously accessing the django.contrib.auth.views.logout view (provided it wasn't decorated with django.contrib.auth.decorators.loginrequired as done in the admin). This could allow an attacker to easily create many new session records by sending repeated requests, potentially filling up the session store or causing other users' session records to be evicted.
— Red Hat
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2015-5963?
CVE-2015-5963 has been categorized as a denial of service vulnerability affecting certain versions of Django.
How do I fix CVE-2015-5963?
The vulnerability CVE-2015-5963 can be fixed by upgrading Django to version 1.4.22, 1.7.10, or 1.8.4 or later.
Which Django versions are affected by CVE-2015-5963?
CVE-2015-5963 affects Django versions 1.8.x before 1.8.4, 1.7.x before 1.7.10, and 1.4.x before 1.4.22.
What type of attack is possible with CVE-2015-5963?
CVE-2015-5963 allows remote attackers to cause a denial of service through excessive session store consumption or removal of session records.
Is there a workaround for CVE-2015-5963 if I cannot upgrade?
While upgrading is the best solution for CVE-2015-5963, you may consider implementing rate limiting to mitigate potential abuse.