CVE-2015-3982 Django allows user sessions hijacking via an empty string in the session key
Remote attackers can hijack user sessions in Django applications using the cached_db backend by exploiting improper session flushing.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2015-3982?
CVE-2015-3982 is a medium-severity authentication bypass vulnerability in Djangoproject Django, published on 2 Jun 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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.
Which versions are affected by CVE-2015-3982?
3 open source packages ship an affected version, including django and Django. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
django PyPI | From 1.8 | 1.8.2 |
django PyPI | From 1.8a1 | 1.8.2 |
Django PyPI | From 1.8a1 | 1.8.2 |
Products include Djangoproject Django.
How do I fix CVE-2015-3982?
Upgrade django to 1.8.2 or later.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2015-3982 being exploited?
There is no known exploitation of CVE-2015-3982 in the wild and no public exploit code.
Other vulnerabilities in Djangoproject Django
- CVE-2026-4277 Privilege abuse in GenericInlineModelAdmin
- CVE-2024-53908 Django SQL injection in HasKey(lhs, rhs) on Oracle
- CVE-2024-42005 Django SQL injection vulnerability
- CVE-2023-31047 Django bypasses validation when using one form field to upload multiple files
- CVE-2022-34265 Django `Trunc()` and `Extract()` database functions vulnerable to SQL Injection
Sources
Also known as GHSA-6wgp-fwfm-mxp3, PYSEC-2015-19.