|
django
|
4.0.5
|
<4.2.14 ,
>=5.0a1,<5.0.7
|
show Affected versions of Django are affected by a directory-traversal vulnerability in the Storage.save() method. Derived classes of the django.core.files.storage.Storage base class that overrides the generate_filename() method without replicating the file path validations existing in the parent class could allow for directory traversal via certain inputs when calling save(). This could enable an attacker to manipulate file paths and access unintended directories. |
|
django
|
4.0.5
|
>=5.2,<5.2.2 ,
>=5.0a1,<5.1.10 ,
<4.2.22
|
show An issue was discovered in Django 5.2 before 5.2.3, 5.1 before 5.1.11, and 4.2 before 4.2.23. Internal HTTP response logging does not escape request.path, which allows remote attackers to potentially manipulate log output via crafted URLs. This may lead to log injection or forgery when logs are viewed in terminals or processed by external systems. |
|
django
|
4.0.5
|
<3.2.25 ,
>=4.0a1,<4.2.11 ,
>=5.0a1,<5.0.3
|
show Affected versions of Django are vulnerable to potential regular expression denial-of-service (REDoS). django.utils.text.Truncator.words() method (with html=True) and truncatewords_html template filter were subject to a potential regular expression denial-of-service attack using a suitably crafted string (follow up to CVE-2019-14232 and CVE-2023-43665). |
|
django
|
4.0.5
|
<4.2.14 ,
>=5.0a1,<5.0.7
|
show Affected versions of Django are affected by a username enumeration vulnerability caused by timing differences in the django.contrib.auth.backends.ModelBackend.authenticate() method. This method allowed remote attackers to enumerate users through a timing attack involving login requests for users with unusable passwords. The timing difference in the authentication process exposed whether a username was valid or not, potentially aiding attackers in gaining unauthorized access. |
|
django
|
4.0.5
|
>=5.2.0,<5.2.1 ,
>=5.1.0,<5.1.9 ,
<4.2.21
|
show An issue was discovered in Django 4.2 before 4.2.21, 5.1 before 5.1.9, and 5.2 before 5.2.1. The django.utils.html.strip_tags() function is vulnerable to a potential denial-of-service (slow performance) when processing inputs containing large sequences of incomplete HTML tags. The template filter striptags is also vulnerable, because it is built on top of strip_tags(). |
|
django
|
4.0.5
|
<4.2.15 ,
>=5.0a1,<5.0.8
|
show Affected versions of Django has a potential SQL injection vulnerability in the QuerySet.values() and QuerySet.values_list() methods. When used on models with a JSONField, these methods are susceptible to SQL injection through column aliases if a crafted JSON object key is passed as an argument. |
|
django
|
4.0.5
|
<4.2.14 ,
>=5.0a1,<5.0.7
|
show Affected versions of Django are affected by a potential denial-of-service vulnerability in the django.utils.html.urlize() function. The urlize and urlizetrunc template filters were susceptible to a denial-of-service attack via certain inputs containing many brackets. An attacker could exploit this vulnerability to cause significant delays or crashes in the affected application. |
|
django
|
4.0.5
|
<4.2.16 ,
>=5.0a1,<5.0.9 ,
>=5.1a1,<5.1.1
|
show A security vulnerability has been discovered in certain versions of Django, affecting the password reset functionality. The PasswordResetForm class in django.contrib.auth.forms inadvertently allowed attackers to enumerate user email addresses by exploiting unhandled exceptions during the email sending process. This could be done by issuing password reset requests and observing the responses. Django has implemented a fix where these exceptions are now caught and logged using the django.contrib.auth logger, preventing potential information leakage through error responses. |
|
django
|
4.0.5
|
<3.2.16 ,
>=4.0a1,<4.0.8 ,
>=4.1a1,<4.1.2
|
show In Django 3.2 before 3.2.16, 4.0 before 4.0.8, and 4.1 before 4.1.2, internationalized URLs were subject to a potential denial of service attack via the locale parameter, which is treated as a regular expression. |
|
django
|
4.0.5
|
<3.2.21 ,
>=4.0a1,<4.1.11 ,
>=4.2a1,<4.2.5
|
show Affected versions of Django are vulnerable to potential Denial of Service via certain inputs with a very large number of Unicode characters in django.utils.encoding.uri_to_iri(). |
|
django
|
4.0.5
|
<4.2.15 ,
>=5.0a1,<5.0.8
|
show Django addresses a memory exhaustion issue in django.utils.numberformat.floatformat(). When floatformat receives a string representation of a number in scientific notation with a large exponent, it could lead to excessive memory consumption. To prevent this, decimals with more than 200 digits are now returned as-is. |
|
django
|
4.0.5
|
<3.2.19 ,
>=4.0a1,<4.1.9 ,
>=4.2a1,<4.2.1
|
show Django 4.2.1, 4.1.9 and 3.2.19 include a fix for CVE-2023-31047: In Django 3.2 before 3.2.19, 4.x before 4.1.9, and 4.2 before 4.2.1, it was possible to bypass validation when using one form field to upload multiple files. This multiple upload has never been supported by forms.FileField or forms.ImageField (only the last uploaded file was validated). However, Django's "Uploading multiple files" documentation suggested otherwise.
https://www.djangoproject.com/weblog/2023/may/03/security-releases |
|
django
|
4.0.5
|
<4.2.18 ,
>=5.0.0,<5.0.11 ,
>=5.1.0,<5.1.5
|
show Affected versions of Django are vulnerable to a potential denial-of-service attack due to improper IPv6 validation. The lack of upper limit enforcement for input strings in clean_ipv6_address, is_valid_ipv6_address, and the django.forms.GenericIPAddressField form field allowed attackers to exploit overly long inputs, causing resource exhaustion. The vulnerability is addressed by defining a max_length of 39 characters for affected form fields. The django.db.models.GenericIPAddressField model field was not impacted. Users should upgrade promptly. |
|
django
|
4.0.5
|
<4.2.16 ,
>=5.0a1,<5.0.9 ,
>=5.1a1,<5.1.1
|
show A potential denial-of-service vulnerability has been identified in Django's urlize() and urlizetrunc() functions in django.utils.html. This vulnerability can be triggered by inputting huge strings containing a specific sequence of characters. |
|
django
|
4.0.5
|
<3.2.17 ,
>=4.0a1,<4.0.9 ,
>=4.1a1,<4.1.6
|
show Django 3.2.17, 4.0.9 and 4.1.6 includes a fix for CVE-2023-23969: In Django 3.2 before 3.2.17, 4.0 before 4.0.9, and 4.1 before 4.1.6, the parsed values of Accept-Language headers are cached in order to avoid repetitive parsing. This leads to a potential denial-of-service vector via excessive memory usage if the raw value of Accept-Language headers is very large.
https://www.djangoproject.com/weblog/2023/feb/01/security-releases |
|
django
|
4.0.5
|
<3.2.14 ,
>=4.0a1,<4.0.6
|
show Django 3.2.14 and 4.0.6 include a fix for CVE-2022-34265: Potential SQL injection via Trunc(kind) and Extract(lookup_name) arguments.
https://www.djangoproject.com/weblog/2022/jul/04/security-releases |
|
django
|
4.0.5
|
<4.2.17 ,
>=5.0a1,<5.0.10 ,
>=5.1a1,<5.1.4
|
show Django affected versions are vulnerable to a potential SQL injection in the HasKey(lhs, rhs) lookup on Oracle databases. The vulnerability arises when untrusted data is directly used as the lhs value in the django.db.models.fields.json.HasKey lookup. However, applications using the jsonfield.has_key lookup with the __ syntax remain unaffected by this issue. |
|
django
|
4.0.5
|
<3.2.18 ,
>=4.0a1,<4.0.10 ,
>=4.1a1,<4.1.7
|
show Django 4.1.7, 4.0.10 and 3.2.18 include a fix for CVE-2023-24580: Potential denial-of-service vulnerability in file uploads.
https://www.djangoproject.com/weblog/2023/feb/14/security-releases |
|
django
|
4.0.5
|
<4.2.17 ,
>=5.0a1,<5.0.10 ,
>=5.1a1,<5.1.4
|
show Affected versions of Django are vulnerable to a potential denial-of-service (DoS) attack in the `django.utils.html.strip_tags()` method. The vulnerability occurs when the `strip_tags()` method or the `striptags` template filter processes inputs containing large sequences of nested, incomplete HTML entities. |
|
django
|
4.0.5
|
<3.2.24 ,
>=4.0a1,<4.2.10 ,
>=5.0a1,<5.0.2
|
show Affected versions of Django are vulnerable to potential denial-of-service in intcomma template filter when used with very long strings. |
|
django
|
4.0.5
|
<4.2.20 ,
>=5.0a1,<5.0.13 ,
>=5.1a1,<5.1.7
|
show Affected versions of Django are vulnerable to a potential denial-of-service in django.utils.text.wrap(). The django.utils.text.wrap() and wordwrap template filter were subject to a potential denial-of-service attack when used with very long strings. |
|
django
|
4.0.5
|
<3.2.23 ,
>=4.0a1,<4.1.13 ,
>=4.2a1,<4.2.7
|
show Django 4.2.7, 4.1.13 and 3.2.23 include a fix for CVE-2023-46695: Potential denial of service vulnerability in UsernameField on Windows.
https://www.djangoproject.com/weblog/2023/nov/01/security-releases |
|
django
|
4.0.5
|
<4.2.15 ,
>=5.0a1,<5.0.8
|
show Django has a potential denial-of-service vulnerability in django.utils.html.urlize() and AdminURLFieldWidget. The urlize and urlizetrunc functions, along with AdminURLFieldWidget, are vulnerable to denial-of-service attacks when handling inputs with a very large number of Unicode characters. |
|
django
|
4.0.5
|
<4.2.14 ,
>=5.0a1,<5.0.7
|
show Affected versions of Django are potentially vulnerable to denial-of-service via the get_supported_language_variant() method. This method was susceptible to a denial-of-service attack when used with very long strings containing specific characters. Exploiting this vulnerability could cause significant delays or crashes in the affected application, potentially leading to service disruption. |
|
django
|
4.0.5
|
<3.2.22 ,
>=4.0a1,<4.1.12 ,
>=4.2a1,<4.2.6
|
show Affected versions of Django are vulnerable to Denial-of-Service via django.utils.text.Truncator. The django.utils.text.Truncator chars() and words() methods (when used with html=True) are subject to a potential DoS (denial of service) attack via certain inputs with very long, potentially malformed HTML text. The chars() and words() methods are used to implement the truncatechars_html and truncatewords_html template filters, which are thus also vulnerable. NOTE: this issue exists because of an incomplete fix for CVE-2019-14232. |
|
django
|
4.0.5
|
>=4.0a1,<4.1.10 ,
>=4.2a1,<4.2.3 ,
<3.2.20
|
show Affected versions of Django are vulnerable to a potential ReDoS (regular expression denial of service) in EmailValidator and URLValidator via a very large number of domain name labels of emails and URLs. |
|
django
|
4.0.5
|
<3.2.15 ,
>=4.0a1,<4.0.7
|
show Django 3.2.15 and 4.0.7 include a fix for CVE-2022-36359: An issue was discovered in the HTTP FileResponse class in Django 3.2 before 3.2.15 and 4.0 before 4.0.7. An application is vulnerable to a reflected file download (RFD) attack that sets the Content-Disposition header of a FileResponse when the filename is derived from user-supplied input.
https://www.djangoproject.com/weblog/2022/aug/03/security-releases |
Update botocore from 1.27.19 to 1.27.75
