| 1 |
=========================== |
| 2 |
Django 4.2.17 release notes |
| 3 |
=========================== |
| 4 |
|
| 5 |
*December 4, 2024* |
| 6 |
|
| 7 |
Django 4.2.17 fixes one security issue with severity "high" and one security |
| 8 |
issue with severity "moderate" in 4.2.16. |
| 9 |
|
| 10 |
CVE-2024-53907: Denial-of-service possibility in ``strip_tags()`` |
| 11 |
================================================================= |
| 12 |
|
| 13 |
:func:`~django.utils.html.strip_tags` would be extremely slow to evaluate |
| 14 |
certain inputs containing large sequences of nested incomplete HTML entities. |
| 15 |
The ``strip_tags()`` method is used to implement the corresponding |
| 16 |
:tfilter:`striptags` template filter, which was thus also vulnerable. |
| 17 |
|
| 18 |
``strip_tags()`` now has an upper limit of recursive calls to ``HTMLParser`` |
| 19 |
before raising a :exc:`.SuspiciousOperation` exception. |
| 20 |
|
| 21 |
Remember that absolutely NO guarantee is provided about the results of |
| 22 |
``strip_tags()`` being HTML safe. So NEVER mark safe the result of a |
| 23 |
``strip_tags()`` call without escaping it first, for example with |
| 24 |
:func:`django.utils.html.escape`. |
| 25 |
|
| 26 |
CVE-2024-53908: Potential SQL injection via ``HasKey(lhs, rhs)`` on Oracle |
| 27 |
========================================================================== |
| 28 |
|
| 29 |
Direct usage of the ``django.db.models.fields.json.HasKey`` lookup on Oracle |
| 30 |
was subject to SQL injection if untrusted data was used as a ``lhs`` value. |
| 31 |
|
| 32 |
Applications that use the :lookup:`has_key <jsonfield.has_key>` lookup through |
| 33 |
the ``__`` syntax are unaffected. |