USN-6888-1: Django vulnerabilities
Elias Myllymäki discovered that Django incorrectly handled certain inputs with a large number of brackets. A remote attacker could possibly use this issue to cause Django to consume resources or stop responding, resulting in a denial of service. (CVE-2024-38875) It was discovered that Django incorrectly handled authenticating users with unusable passwords. A remote attacker could possibly use this issue to perform a timing attack and enumerate users. (CVE-2024-39329) Josh Schneier discovered that Django incorrectly handled file path validation when the storage class is being derived. A remote attacker could possibly use this issue to save files into arbitrary directories. (CVE-2024-39330) It was discovered that Django incorrectly handled certain long strings that included a specific set of characters. A remote attacker could possibly use this issue to cause Django to consume resources or stop responding, resulting in a denial of service. (CVE-2024-39614)
Affected Software
Event History
Child vulnerabilities
Contains the following vulnerabilities.
Frequently Asked Questions
What is the severity of USN-6888-1?
The severity of USN-6888-1 is classified as a denial of service vulnerability.
How do I fix USN-6888-1?
To fix USN-6888-1, update the python3-django package to the latest version available for your Ubuntu release.
Which versions of python3-django are affected by USN-6888-1?
USN-6888-1 affects python3-django versions up to 3:4.2.11-1ubuntu1.1, 3:4.2.4-1ubuntu2.3, 2:3.2.12-2ubuntu1.12, and 2:2.2.12-1ubuntu0.23.
What are the potential impacts of USN-6888-1?
The potential impacts of USN-6888-1 include high resource consumption or complete unresponsiveness of the Django application.
Who discovered USN-6888-1?
USN-6888-1 was discovered by security researcher Elias Myllymäki.