Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
requirements: upgrade Django to 4.2.14 (#1189)
This to address the following recent security issues: ``` Name | Version | ID | Fix Versions | Description --- | --- | --- | --- | --- django | 4.2.11 | PYSEC-2024-58 | 4.2.14,5.0.7 | An issue was discovered in Django 5.0 before 5.0.7 and 4.2 before 4.2.14. Derived classes of the django.core.files.storage.Storage base class, when they override generate_filename() without replicating the file-path validations from the parent class, potentially allow directory traversal via certain inputs during a save() call. (Built-in Storage sub-classes are unaffected.) django | 4.2.11 | PYSEC-2024-57 | 4.2.14,5.0.7 | An issue was discovered in Django 5.0 before 5.0.7 and 4.2 before 4.2.14. The django.contrib.auth.backends.ModelBackend.authenticate() method allows remote attackers to enumerate users via a timing attack involving login requests for users with an unusable password. django | 4.2.11 | PYSEC-2024-56 | 4.2.14,5.0.7 | An issue was discovered in Django 4.2 before 4.2.14 and 5.0 before 5.0.7. urlize and urlizetrunc were subject to a potential denial of service attack via certain inputs with a very large number of brackets. django | 4.2.11 | PYSEC-2024-59 | 4.2.14,5.0.7 | An issue was discovered in Django 5.0 before 5.0.7 and 4.2 before 4.2.14. get_supported_language_variant() was subject to a potential denial-of-service attack when used with very long strings containing specific characters. ``` Changelog: https://docs.djangoproject.com/en/5.0/releases/#id1
- Loading branch information