|
py
|
1.11.0
|
<=1.11.0
|
show ** DISPUTED ** Py throughout 1.11.0 allows remote attackers to conduct a ReDoS (Regular expression Denial of Service) attack via a Subversion repository with crafted info data because the InfoSvnCommand argument is mishandled.
https://github.com/pytest-dev/py/issues/287 |
|
django
|
4.1.6
|
<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.1.6
|
>=2.1a1, <3.2.15 ,
>=4.0a1, <4.0.7 ,
>=4.1a1, <4.2a1
|
show Affected versions of the `django` package are vulnerable to Download of Code Without Integrity Check due to improper handling of user-supplied input in the HTTP FileResponse class. The vulnerability arises because the Content-Disposition header of a FileResponse can be set using a filename derived from user input without sufficient validation. An attacker can exploit this by crafting a request that causes a file with malicious content to be downloaded, potentially executing arbitrary code on the client system when the file is opened. |
|
django
|
4.1.6
|
<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.1.6
|
<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.1.6
|
<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.1.6
|
<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.1.6
|
<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.1.6
|
<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.1.6
|
<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.1.6
|
<4.2.26 ,
>=5.1a1,<5.1.14 ,
>=5.2a1,<5.2.8
|
show CVE-2025-64458: Affected versions of the Django package are vulnerable to Denial of Service (DoS) due to slow Unicode NFKC normalization on Windows being applied to untrusted inputs. The django.contrib.auth.views.LoginView and django.contrib.auth.views.LogoutView, and django.views.i18n.set_language normalize user-controlled strings using Python’s NFKC algorithm, which is unusually slow on Windows for huge Unicode sequences and can be triggered to consume excessive CPU. |
|
django
|
4.1.6
|
<4.2.26 ,
>=5.1a1,<5.1.14 ,
>=5.2a1,<5.2.8
|
show CVE-2025-64459: Affected versions of the Django package are vulnerable to SQL Injection due to improper input validation, allowing the internal _connector keyword argument to be accepted from untrusted dictionaries via expansion. The .filter(), .exclude(), and .get() methods on QuerySet, as well as the Q class, resolve **kwargs and will treat a supplied _connector value as the logical connector without constraining it to the expected set (AND/OR), permitting attacker-controlled tokens to influence SQL predicate construction. |
|
django
|
4.1.6
|
<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.1.6
|
<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.1.6
|
<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.1.6
|
>=5.2a1,<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.1.6
|
<4.2.21 ,
>=5.2a1,<5.2.1 ,
>=5.1.0a1,<5.1.9
|
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.1.6
|
<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.1.6
|
<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.1.6
|
>=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.1.6
|
<4.2.24 ,
>=5.0a1,<5.1.12 ,
>=5.2a1,<5.2.6
|
show Affected versions of the Django package are vulnerable to SQL Injection due to insufficient input sanitization in FilteredRelation column aliases. The FilteredRelation class fails to properly validate or escape column alias names when they are provided through dictionary expansion as keyword arguments to QuerySet.annotate() or QuerySet.alias() methods, allowing malicious SQL code to be injected directly into the generated database queries. |
|
django
|
4.1.6
|
<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.1.6
|
<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.1.6
|
<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.1.6
|
<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.1.6
|
<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. |
|
sqlparse
|
0.4.3
|
>=0.1.15,<0.4.4
|
show Sqlparse 0.4.4 includes a fix for CVE-2023-30608: Parser contains a regular expression that is vulnerable to ReDOS (Regular Expression Denial of Service).
https://github.com/andialbrecht/sqlparse/security/advisories/GHSA-rrm6-wvj7-cwh2 |
|
sqlparse
|
0.4.3
|
<0.5.0
|
show Sqlparse 0.5.0 addresses a potential denial of service (DoS) vulnerability related to recursion errors in deeply nested SQL statements. To mitigate this issue, the update replaces recursion errors with a general SQLParseError, improving the resilience and stability of the parsing process. |
Update boto3 from 1.26.69 to 1.26.133
