CVE-2015-8213 Django settings leak in date template filter
Remote attackers can obtain sensitive application secrets like SECRET_KEY by manipulating date/time format settings in Django.
- 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-8213?
CVE-2015-8213 is a medium-severity vulnerability in Djangoproject Django, published on 7 Dec 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
The get_format function in utils/formats.py in Django before 1.7.x before 1.7.11, 1.8.x before 1.8.7, and 1.9.x before 1.9rc2 might allow remote attackers to obtain sensitive application secrets via a settings key in place of a date/time format setting, as demonstrated by SECRET_KEY.
Weakness: CWE-200
Which versions are affected by CVE-2015-8213?
7 open source packages ship an affected version, including django and Django. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
django PyPI | All versions | 1.7.11, 1.8.7, 1.9rc2 |
django PyPI | From 1.7 | 1.7.11 |
django PyPI | From 1.8a1 | 1.8.7 |
django PyPI | From 1.9a1 | 1.9rc2 |
Django PyPI | From 1.7 | 1.7.11 |
Django PyPI | From 1.8a1 | 1.8.7 |
1 more packages
Django PyPI | From 1.9a1 | 1.9rc2 |
Linux distribution packages (16)
python-django Red Hat:openstack-optools:7::el7 | All versions | 0:1.6.11-4.el7ost |
python-django-bash-completion Red Hat:openstack-optools:7::el7 | All versions | 0:1.6.11-4.el7ost |
python-django Red Hat:openstack:5::el6 | All versions | 0:1.6.11-4.el6ost |
python-django-bash-completion Red Hat:openstack:5::el6 | All versions | 0:1.6.11-4.el6ost |
python-django-doc Red Hat:openstack:5::el6 | All versions | 0:1.6.11-4.el6ost |
python-django Red Hat:openstack:5::el7 | All versions | 0:1.6.11-4.el7ost |
python-django-bash-completion Red Hat:openstack:5::el7 | All versions | 0:1.6.11-4.el7ost |
python-django-doc Red Hat:openstack:5::el7 | All versions | 0:1.6.11-4.el7ost |
python-django Red Hat:openstack:6::el7 | All versions | 0:1.6.11-4.el7ost |
python-django-bash-completion Red Hat:openstack:6::el7 | All versions | 0:1.6.11-4.el7ost |
python-django-doc Red Hat:openstack:6::el7 | All versions | 0:1.6.11-4.el7ost |
python-django Red Hat:openstack:7::el7 | All versions | 0:1.8.7-1.el7 |
python-django-bash-completion Red Hat:openstack:7::el7 | All versions | 0:1.8.7-1.el7 |
python-django-doc Red Hat:openstack:7::el7 | All versions | 0:1.8.7-1.el7 |
python-Django SUSE:Enterprise Storage 1.0 | All versions | 1.6.11-11.1 |
python-Django SUSE:OpenStack Cloud 5 | All versions | 1.6.11-13.1 |
Products include Djangoproject Django.
How do I fix CVE-2015-8213?
Upgrade django to a fixed version for your release line: 1.7.11, 1.8.7 or 1.9rc2.
Is CVE-2015-8213 being exploited?
There is no known exploitation of CVE-2015-8213 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 DEBIAN-CVE-2015-8213, DLA-349-1, DSA-3404-1, GHSA-6wcr-wcqm-3mfh, MGASA-2015-0463, PYSEC-2015-11 and 9 more.