| 1 |
=========================== |
| 2 |
Django 1.7.11 release notes |
| 3 |
=========================== |
| 4 |
|
| 5 |
*November 24, 2015* |
| 6 |
|
| 7 |
Django 1.7.11 fixes a security issue and a data loss bug in 1.7.10. |
| 8 |
|
| 9 |
Fixed settings leak possibility in ``date`` template filter |
| 10 |
=========================================================== |
| 11 |
|
| 12 |
If an application allows users to specify an unvalidated format for dates and |
| 13 |
passes this format to the :tfilter:`date` filter, e.g. |
| 14 |
``{{ last_updated|date:user_date_format }}``, then a malicious user could |
| 15 |
obtain any secret in the application's settings by specifying a settings key |
| 16 |
instead of a date format. e.g. ``"SECRET_KEY"`` instead of ``"j/m/Y"``. |
| 17 |
|
| 18 |
To remedy this, the underlying function used by the ``date`` template filter, |
| 19 |
``django.utils.formats.get_format()``, now only allows accessing the date/time |
| 20 |
formatting settings. |
| 21 |
|
| 22 |
Bugfixes |
| 23 |
======== |
| 24 |
|
| 25 |
* Fixed a data loss possibility with :class:`~django.db.models.Prefetch` if |
| 26 |
``to_attr`` is set to a ``ManyToManyField`` (:ticket:`25693`). |