CVE-2015-5963: High severity django vulnerability

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

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

46 affected componentsFixes available
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
djangoproject Django=1.4
djangoproject Django=1.4.1
djangoproject Django=1.4.2
djangoproject Django=1.4.4
djangoproject Django=1.4.5
djangoproject Django=1.4.6
djangoproject Django=1.4.7
djangoproject Django=1.4.8
djangoproject Django=1.4.9
djangoproject Django=1.4.10
djangoproject Django=1.4.11
djangoproject Django=1.4.12
djangoproject Django=1.4.13
djangoproject Django=1.4.14
djangoproject Django=1.4.17
djangoproject Django=1.4.19
djangoproject Django=1.4.20
djangoproject Django=1.4.21
djangoproject Django=1.7-beta1
djangoproject Django=1.7-beta2
djangoproject Django=1.7-beta3
djangoproject Django=1.7-beta4
djangoproject Django=1.7-rc1
djangoproject Django=1.7-rc2
djangoproject Django=1.7-rc3
djangoproject Django=1.7.1
djangoproject Django=1.7.2
djangoproject Django=1.7.3
djangoproject Django=1.7.4
djangoproject Django=1.7.5
djangoproject Django=1.7.6
djangoproject Django=1.7.7
djangoproject Django=1.7.8
djangoproject Django=1.7.9
djangoproject Django=1.8-beta1
djangoproject Django=1.8.0
djangoproject Django=1.8.1
djangoproject Django=1.8.2
djangoproject Django=1.8.3
Oracle Solaris=11.3
Canonical Ubuntu Linux=12.04
Canonical Ubuntu Linux=14.04
Canonical Ubuntu Linux=15.04

Event History

Aug 12, 2015
Data Sourced
via Red Hat·01:02 PM
DescriptionSeverityAffected Software
Aug 24, 2015
CVE Published
via MITRE·02:00 PM
Data Sourced
via MITRE·02:00 PM
Description
May 17, 2022
Advisory Published
via GitHub·12:36 AM

Frequently Asked Questions

1

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.

2

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.

3

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.

4

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.

5

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203