django
|
1.11
|
<2.2.28 ,
>=3.0a1,<3.2.13 ,
>=4.0a1,<4.0.4
|
show Django 2.2.28, 3.2.13 and 4.0.4 include a fix for CVE-2022-28347: A SQL injection issue was discovered in QuerySet.explain() in Django 2.2 before 2.2.28, 3.2 before 3.2.13, and 4.0 before 4.0.4. This occurs by passing a crafted dictionary (with dictionary expansion) as the **options argument, and placing the injection payload in an option name.
https://www.djangoproject.com/weblog/2022/apr/11/security-releases
|
django
|
1.11
|
>=1.11a1,<1.11.22 ,
>=2.2a1,<2.2.3 ,
>=2.1a1,<2.1.10
|
show An issue was discovered in Django 1.11 before 1.11.22, 2.1 before 2.1.10, and 2.2 before 2.2.3. An HTTP request is not redirected to HTTPS when the SECURE_PROXY_SSL_HEADER and SECURE_SSL_REDIRECT settings are used, and the proxy connects to Django via HTTPS. In other words, django.http.HttpRequest.scheme has incorrect behavior when a client uses HTTP.
|
django
|
1.11
|
<2.1.9 ,
>=2.2a1,<2.2.2
|
show Django versions 2.1.9 and 2.2.2 include a patched bundled jQuery version to avoid a Prototype Pollution vulnerability.
|
django
|
1.11
|
<2.2.27 ,
>=3.0a1,<3.2.12 ,
>=4.0a1,<4.0.2
|
show The {% debug %} template tag in Django 2.2 before 2.2.27, 3.2 before 3.2.12, and 4.0 before 4.0.2 does not properly encode the current context. This may lead to XSS.
|
django
|
1.11
|
<2.2.26 ,
>=3.0a1,<3.2.11 ,
>=4.0a1,<4.0.1
|
show Django 2.2.26, 3.2.11 and 4.0.1 include a fix for CVE-2021-45115: UserAttributeSimilarityValidator incurred significant overhead in evaluating a submitted password that was artificially large in relation to the comparison values. In a situation where access to user registration was unrestricted, this provided a potential vector for a denial-of-service attack.
https://www.djangoproject.com/weblog/2022/jan/04/security-releases/
|
django
|
1.11
|
>=3.0.0a1,<3.1.12 ,
>=3.2.0a1,<3.2.4 ,
<2.2.24
|
show Django 2.2.24, 3.1.12, and 3.2.4 include a fix for CVE-2021-33571: In Django 2.2 before 2.2.24, 3.x before 3.1.12, and 3.2 before 3.2.4, URLValidator, validate_ipv4_address, and validate_ipv46_address do not prohibit leading zero characters in octal literals. This may allow a bypass of access control that is based on IP addresses. (validate_ipv4_address and validate_ipv46_address are unaffected with Python 3.9.5+).
https://www.djangoproject.com/weblog/2021/jun/02/security-releases
|
django
|
1.11
|
>=1.11a1,<1.11.28 ,
>=2.0a1,<2.2.10 ,
>=3.0a1,<3.0.3
|
show Django 1.11.28, 2.2.10 and 3.0.3 include a fix for CVE-2020-7471: SQL Injection if untrusted data is used as a StringAgg delimiter (e.g., in Django applications that offer downloads of data as a series of rows with a user-specified column delimiter). By passing a suitably crafted delimiter to a contrib.postgres.aggregates.StringAgg instance, it was possible to break escaping and inject malicious SQL.
|
django
|
1.11
|
<2.2.25 ,
>=3.2a1,<3.2.10 ,
>=3.1a1,<3.1.14
|
show Django versions 2.2.25, 3.1.14 and 3.2.10 include a fix for CVE-2021-44420: In Django 2.2 before 2.2.25, 3.1 before 3.1.14, and 3.2 before 3.2.10, HTTP requests for URLs with trailing newlines could bypass upstream access control based on URL paths.
https://www.djangoproject.com/weblog/2021/dec/07/security-releases/
|
django
|
1.11
|
>=1.11a1,<1.11.23 ,
>=2.0a1,<2.1.11 ,
>=2.2a1,<2.2.4
|
show Django 1.11.23, 2.1.11, and 2.2.4 include a fix for CVE-2019-14233: Due to the behavior of the underlying HTMLParser, django.utils.html.strip_tags would be extremely slow to evaluate certain inputs containing large sequences of nested incomplete HTML entities.
|
django
|
1.11
|
>=1.11a1,<1.11.23 ,
>=2.0a1,<2.1.11 ,
>=2.2a1,<2.2.4
|
show Django 1.11.23, 2.1.11 and 2.2.4 includes a fix for CVE-2019-14235: If passed certain inputs, django.utils.encoding.uri_to_iri could lead to significant memory usage due to a recursion when repercent-encoding invalid UTF-8 octet sequences.
|
django
|
1.11
|
>=2.1a1,<2.1.1 ,
>=2.0a1,<2.0.9 ,
<1.11.16
|
show Django 1.11.16, 2.0.9 and 2.1.1 include a fix for a Race Condition vulnerability that could lead to data loss.
https://github.com/django/django/commit/221ef69a9b89262456bb7abe0e5a4b2fda4a0695
|
django
|
1.11
|
<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
|
1.11
|
<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
|
django
|
1.11
|
<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
|
1.11
|
>=3.0a1,<3.0.13 ,
>=3.1a1,<3.1.7 ,
<2.2.19
|
show Django versions 2.2.19, 3.0.13 and 3.1.7 include a fix for CVE-2021-23336: Web cache poisoning via 'django.utils.http.limited_parse_qsl()'. Django contains a copy of 'urllib.parse.parse_qsl' which was added to backport some security fixes. A further security fix has been issued recently such that 'parse_qsl(' no longer allows using ';' as a query parameter separator by default.
|
django
|
1.11
|
<2.2.26 ,
>=3.0a1,<3.2.11 ,
>=4.0a1,<4.0.1
|
show Django 2.2.26, 3.2.11 and 4.0.1 include a fix for CVE-2021-45116: An issue was discovered in Django 2.2 before 2.2.26, 3.2 before 3.2.11, and 4.0 before 4.0.1. Due to leveraging the Django Template Language's variable resolution logic, the dictsort template filter was potentially vulnerable to information disclosure, or an unintended method call, if passed a suitably crafted key.
https://www.djangoproject.com/weblog/2022/jan/04/security-releases
|
django
|
1.11
|
<2.2.26 ,
>=3.0a1,<3.2.11 ,
>=4.0a1,<4.0.1
|
show Django 2.2.26, 3.2.11 and 4.0.1 include a fix for CVE-2021-45452: Storage.save in Django 2.2 before 2.2.26, 3.2 before 3.2.11, and 4.0 before 4.0.1 allows directory traversal if crafted filenames are directly passed to it.
https://www.djangoproject.com/weblog/2022/jan/04/security-releases/
|
django
|
1.11
|
<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
|
1.11
|
<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
|
1.11
|
>=1.11a1,<1.11.23 ,
>=2.0a1,<2.1.11 ,
>=2.2a1,<2.2.4
|
show Django 1.11.23, 2.1.11 and 2.2.4 include a fix for CVE-2019-14234: Due to an error in shallow key transformation, key and index lookups for django.contrib.postgres.fields.JSONField, and key lookups for django.contrib.postgres.fields.HStoreField, were subject to SQL injection. This could, for example, be exploited via crafted use of "OR 1=1" in a key or index name to return all records, using a suitably crafted dictionary, with dictionary expansion, as the **kwargs passed to the QuerySet.filter() function.
|
django
|
1.11
|
<1.10.8 ,
>=1.11a1,<1.11.5
|
show Django 1.10.8 and 1.11.5 include a fix for CVE-2017-12794: In Django 1.10.x before 1.10.8 and 1.11.x before 1.11.5, HTML autoescaping was disabled in a portion of the template for the technical 500 debug page. Given the right circumstances, this allowed a cross-site scripting attack. This vulnerability shouldn't affect most production sites since you shouldn't run with "DEBUG = True" (which makes this page accessible) in your production settings.
https://www.djangoproject.com/weblog/2017/sep/05/security-releases
|
django
|
1.11
|
<2.2.27 ,
>=3.0a1,<3.2.12 ,
>=4.0a1,<4.0.2
|
show Django 2.2.27, 3.2.12 and 4.0.2 include a fix for CVE-2022-23833: Denial-of-service possibility in file uploads.
https://www.djangoproject.com/weblog/2022/feb/01/security-releases
|
django
|
1.11
|
<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
|
1.11
|
<2.2.28 ,
>=3.0a1,<3.2.13 ,
>=4.0a1,<4.0.4
|
show Django 2.2.28, 3.2.13 and 4.0.4 include a fix for CVE-2022-28346: An issue was discovered in Django 2.2 before 2.2.28, 3.2 before 3.2.13, and 4.0 before 4.0.4. QuerySet.annotate(), aggregate(), and extra() methods are subject to SQL injection in column aliases via a crafted dictionary (with dictionary expansion) as the passed **kwargs.
https://www.djangoproject.com/weblog/2022/apr/11/security-releases
|
django
|
1.11
|
<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
|
1.11
|
>=2.0a1,<2.0.3 ,
>=1.8a1,<1.8.19 ,
>=1.11a1,<1.11.11
|
show An issue was discovered in Django 2.0 before 2.0.3, 1.11 before 1.11.11, and 1.8 before 1.8.19. The django.utils.html.urlize() function was extremely slow to evaluate certain inputs due to catastrophic backtracking vulnerabilities in two regular expressions (only one regular expression for Django 1.8.x). The urlize() function is used to implement the urlize and urlizetrunc template filters, which were thus vulnerable. See: CVE-2018-7536.
|
django
|
1.11
|
>=2.0a1,<2.0.11 ,
<1.11.19 ,
>=2.1a1,<2.1.6
|
show Django 1.11.19, 2.0.11 and 2.1.6 include a fix for CVE-2019-6975: Uncontrolled Memory Consumption via a malicious attacker-supplied value to the django.utils.numberformat.format() function.
|
django
|
1.11
|
>=1.11a1,<1.11.21 ,
>=2.0a1,<2.1.9 ,
>=2.2a1,<2.2.2
|
show Django 1.11.21, 2.1.9 and 2.2.2 include a fix for CVE-2019-12308: The clickable Current URL value displayed by the AdminURLFieldWidget displays the provided value without validating it as a safe URL. Thus, a non validated value stored in the database, or a value provided as a URL query parameter payload, could result in an clickable JavaScript link.
|
django
|
1.11
|
<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
|
1.11
|
>=1.11a1,<1.11.27 ,
>=2.0a1,<2.2.9 ,
>=3.0a1,<3.0.1
|
show Django 1.11.27, 2.2.9 and 3.0.1 include a fix for CVE-2019-19844: Account takeover. A suitably crafted email address (that is equal to an existing user's email address after case transformation of Unicode characters) would allow an attacker to be sent a password reset token for the matched user account. One mitigation in the new releases is to send password reset tokens only to the registered user email address.
|
django
|
1.11
|
<2.2.16 ,
>=3.0a1,<3.0.10 ,
>=3.1a1,<3.1.1
|
show Django 2.2.16, 3.0.10 and 3.1.1 include a fix for CVE-2020-24583: An issue was discovered in Django 2.2 before 2.2.16, 3.0 before 3.0.10, and 3.1 before 3.1.1 (when Python 3.7+ is used). FILE_UPLOAD_DIRECTORY_PERMISSIONS mode was not applied to intermediate-level directories created in the process of uploading files. It was also not applied to intermediate-level collected static directories when using the collectstatic management command.
#NOTE: This vulnerability affects only users of Python versions above 3.7.
https://www.djangoproject.com/weblog/2020/sep/01/security-releases
|
django
|
1.11
|
<2.2.16 ,
>=3.0a1,<3.0.10 ,
>=3.1a1,<3.1.1
|
show An issue was discovered in Django 2.2 before 2.2.16, 3.0 before 3.0.10, and 3.1 before 3.1.1 (when Python 3.7+ is used). The intermediate-level directories of the filesystem cache had the system's standard umask rather than 0o077.
|
django
|
1.11
|
<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
|
1.11
|
>=3.2a1,<3.2.1 ,
<2.2.21 ,
>=3.0a1,<3.1.9
|
show Django 2.2.21, 3.1.9 and 3.2.1 include a fix for CVE-2021-31542: MultiPartParser, UploadedFile, and FieldFile allowed directory traversal via uploaded files with suitably crafted file names.
https://www.djangoproject.com/weblog/2021/may/04/security-releases
|
django
|
1.11
|
>=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
|
1.11
|
>=2.0a1,<2.0.3 ,
>=1.8a1,<1.8.19 ,
>=1.11a1,<1.11.11
|
show Django 2.0.3, 1.8.19 and 1.11.11 include a fix for CVE-2018-7537: An issue was discovered in Django 2.0 before 2.0.3, 1.11 before 1.11.11, and 1.8 before 1.8.19. If django.utils.text.Truncator's chars() and words() methods were passed the html=True argument, they were extremely slow to evaluate certain inputs due to a catastrophic backtracking vulnerability in a regular expression. The chars() and words() methods are used to implement the truncatechars_html and truncatewords_html template filters, which were thus vulnerable.
|
django
|
1.11
|
>=1.11a1,<1.11.15 ,
>=2.0a1,<2.0.8
|
show django.middleware.common.CommonMiddleware in Django 1.11.x before 1.11.15 and 2.0.x before 2.0.8 has an Open Redirect. A remote user can redirect the target user's browser to an arbitrary site.
|
django
|
1.11
|
<2.2.24 ,
>=3.0a1,<3.1.12 ,
>=3.2a1,<3.2.4
|
show Django before 2.2.24, 3.x before 3.1.12, and 3.2.x before 3.2.4 has a potential directory traversal via django.contrib.admindocs. Staff members could use the TemplateDetailView view to check the existence of arbitrary files. Additionally, if (and only if) the default admindocs templates have been customized by application developers to also show file contents, then not only the existence but also the file contents would have been exposed. In other words, there is directory traversal outside of the template root directories.
https://www.djangoproject.com/weblog/2021/jun/02/security-releases
|
django
|
1.11
|
>=1.11a1,<1.11.23 ,
>=2.0a1,<2.1.11 ,
>=2.2a1,<2.2.4
|
show Django 1.11.23, 2.1.11 and 2.2.4 include a fix for CVE-2019-14232: If django.utils.text.Truncator's chars() and words() methods were passed the html=True argument, they were extremely slow to evaluate certain inputs due to a catastrophic backtracking vulnerability in a regular expression. The chars() and words() methods are used to implement the truncatechars_html and truncatewords_html template filters, which were thus vulnerable.
|
django
|
1.11
|
<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
|
1.11
|
<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-allauth
|
0.32.0
|
<0.47.0
|
show Django-allauth 0.47.0 adds a new setting 'SOCIALACCOUNT_LOGIN_ON_GET' that controls whether or not the endpoints for initiating a social login (for example, "/accounts/google/login/") require a POST request to initiate the handshake. As requiring a POST is more secure, the default of this new setting is 'False'. This is useful to prevent redirect attacks.
|
django-allauth
|
0.32.0
|
<0.54.0
|
show Django-allauth 0.54.0 includes a security fix: Even when account enumeration prevention was turned on, it was possible for an attacker to infer whether or not a given account exists based upon the response time of an authentication attempt.
|
django-allauth
|
0.32.0
|
<0.34.0
|
show On django-allauth before 0.34.0 the "Set Password" view did not properly check whether or not the user already had a usable password set. This allowed an attacker to set the password without providing the current password, but only in case the attacker already gained control over the victim's session.
|
django-allauth
|
0.32.0
|
<0.41.0
|
show Django-allauth 0.41.0 conforms to the general Django 3.0.1, 2.2.9, and 1.11.27 security release. See CVE-2019-19844 and <https://www.djangoproject.com/weblog/2019/dec/18/security-releases/>.
|
django-allauth
|
0.32.0
|
<0.33.0
|
show Django-allauth 0.33 includes a security fix: Leakage of password reset token on a third-party website through the Referer header.
|