| 1 |
=========================== |
| 2 |
Django 2.0.10 release notes |
| 3 |
=========================== |
| 4 |
|
| 5 |
*January 4, 2019* |
| 6 |
|
| 7 |
Django 2.0.10 fixes a security issue and several bugs in 2.0.9. |
| 8 |
|
| 9 |
CVE-2019-3498: Content spoofing possibility in the default 404 page |
| 10 |
------------------------------------------------------------------- |
| 11 |
|
| 12 |
An attacker could craft a malicious URL that could make spoofed content appear |
| 13 |
on the default page generated by the ``django.views.defaults.page_not_found()`` |
| 14 |
view. |
| 15 |
|
| 16 |
The URL path is no longer displayed in the default 404 template and the |
| 17 |
``request_path`` context variable is now quoted to fix the issue for custom |
| 18 |
templates that use the path. |
| 19 |
|
| 20 |
Bugfixes |
| 21 |
======== |
| 22 |
|
| 23 |
* Prevented repetitive calls to ``geos_version_tuple()`` in the ``WKBWriter`` |
| 24 |
class in an attempt to fix a random crash involving ``LooseVersion`` since |
| 25 |
Django 2.0.6 (:ticket:`29959`). |
| 26 |
|
| 27 |
* Fixed a schema corruption issue on SQLite 3.26+. You might have to drop and |
| 28 |
rebuild your SQLite database if you applied a migration while using an older |
| 29 |
version of Django with SQLite 3.26 or later (:ticket:`29182`). |
| 30 |
|
| 31 |
* Prevented SQLite schema alterations while foreign key checks are enabled to |
| 32 |
avoid the possibility of schema corruption (:ticket:`30023`). |