First published: Wed Aug 12 2015(Updated: )
`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.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
pip/Django | >=1.4<1.4.22 | 1.4.22 |
pip/Django | >=1.7<1.7.10 | 1.7.10 |
pip/Django | >=1.8<1.8.4 | 1.8.4 |
Django | =1.4 | |
Django | =1.4.1 | |
Django | =1.4.2 | |
Django | =1.4.4 | |
Django | =1.4.5 | |
Django | =1.4.6 | |
Django | =1.4.7 | |
Django | =1.4.8 | |
Django | =1.4.9 | |
Django | =1.4.10 | |
Django | =1.4.11 | |
Django | =1.4.12 | |
Django | =1.4.13 | |
Django | =1.4.14 | |
Django | =1.4.17 | |
Django | =1.4.19 | |
Django | =1.4.20 | |
Django | =1.4.21 | |
Django | =1.7-beta1 | |
Django | =1.7-beta2 | |
Django | =1.7-beta3 | |
Django | =1.7-beta4 | |
Django | =1.7-rc1 | |
Django | =1.7-rc2 | |
Django | =1.7-rc3 | |
Django | =1.7.1 | |
Django | =1.7.2 | |
Django | =1.7.3 | |
Django | =1.7.4 | |
Django | =1.7.5 | |
Django | =1.7.6 | |
Django | =1.7.7 | |
Django | =1.7.8 | |
Django | =1.7.9 | |
Django | =1.8-beta1 | |
Django | =1.8.0 | |
Django | =1.8.1 | |
Django | =1.8.2 | |
Django | =1.8.3 | |
Oracle Solaris and Zettabyte File System (ZFS) | =11.3 | |
Ubuntu | =12.04 | |
Ubuntu | =14.04 | |
Ubuntu | =15.04 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2015-5963 has been categorized as a denial of service vulnerability affecting certain versions of Django.
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.
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.
CVE-2015-5963 allows remote attackers to cause a denial of service through excessive session store consumption or removal of session records.
While upgrading is the best solution for CVE-2015-5963, you may consider implementing rate limiting to mitigate potential abuse.