output stringlengths 64 2.91k | input stringclasses 1 value | text stringlengths 264 3.14k | instruction stringlengths 53 330 |
|---|---|---|---|
Having vulnarability PVE-2023-54819 Advisory: Django-idom 0.0.2 includes a fix for a potential directory traversal vulnerability.
https://github.com/reactive-python/reactpy-django/pull/45 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-idom version less then 0.0.2 have ### Response: Having vulnarability PVE-2023-54819 Advisory: Django-idom 0.0.2 includes a fix for a potential directory traversal vulnerability.
https://github.com/reactive-python/reactpy-django/pull/45 | what vulnarability does django-idom version less then 0.0.2 have | |
Having vulnarability PVE-2021-25768 Advisory: Django-initial-avatars 0.5.0 uses user_id instead of user_username for the url to prevent information exposure.
https://github.com/axiome-oss/django-initial-avatars/commit/c8741d902ed8596e07966ad358d20f1339a2e35d | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-initial-avatars version less then 0.5.0 have ### Response: Having vulnarability PVE-2021-25768 Advisory: Django-initial-avatars 0.5.0 uses user_id instead of user_username for the url to prevent information exposure.
https://github.com/axiome-oss/django-initial-avatars/commit/c8741d902ed8596e07966ad358d20f1339a2e35d | what vulnarability does django-initial-avatars version less then 0.5.0 have | |
Having vulnarability PVE-2021-25769 Advisory: Django-jet 1.0.4 fixes a security issue with accessing model_lookup_view (when using RelatedFieldAjaxListFilter) without permissions.
https://github.com/geex-arts/django-jet/commit/734f3521d8290f6162847ad0b5c33d8ab5e119a9 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-jet version less then 1.0.4 have ### Response: Having vulnarability PVE-2021-25769 Advisory: Django-jet 1.0.4 fixes a security issue with accessing model_lookup_view (when using RelatedFieldAjaxListFilter) without permissions.
https://github.com/geex-arts/django-jet/commit/734f3521d8290f6162847ad0b5c33d8ab5e119a9 | what vulnarability does django-jet version less then 1.0.4 have | |
Having vulnarability PVE-2021-39370 Advisory: Django-jet-reboot 1.0.4 fixes a security issue with accessing model_lookup_view (when using RelatedFieldAjaxListFilter) without permissions.
https://github.com/assem-ch/django-jet-reboot/commit/734f3521d8290f6162847ad0b5c33d8ab5e119a9 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-jet-reboot version less then 1.0.4 have ### Response: Having vulnarability PVE-2021-39370 Advisory: Django-jet-reboot 1.0.4 fixes a security issue with accessing model_lookup_view (when using RelatedFieldAjaxListFilter) without permissions.
https://github.com/assem-ch/django-jet-reboot/commit/734f3521d8290f6162847ad0b5c33d8ab5e119a9 | what vulnarability does django-jet-reboot version less then 1.0.4 have | |
Having vulnarability PVE-2022-49483 Advisory: Django-jinja-knockout 0.4.1 adds more sanity checks in queries and views modules.
https://github.com/Dmitri-Sintsov/django-jinja-knockout/commit/0c427d13b3de32a2b69c24927b95fc2e46c9a16c
https://github.com/Dmitri-Sintsov/django-jinja-knockout/commit/30c41225e366e0010da47aeeb1ac2e1f2c46f54d | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-jinja-knockout version less then 0.4.1 have ### Response: Having vulnarability PVE-2022-49483 Advisory: Django-jinja-knockout 0.4.1 adds more sanity checks in queries and views modules.
https://github.com/Dmitri-Sintsov/django-jinja-knockout/commit/0c427d13b3de32a2b69c24927b95fc2e46c9a16c
https://github.com/Dmitri-Sintsov/django-jinja-knockout/commit/30c41225e366e0010da47aeeb1ac2e1f2c46f54d | what vulnarability does django-jinja-knockout version less then 0.4.1 have | |
Having vulnarability PVE-2022-51463 Advisory: Django-js-error-hook 0.2 adds CSRF protection by default.
https://github.com/jojax/django-js-error-hook/commit/1d524883b6bcc1e4a6a4bc580c87dfd326828dc9 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-js-error-hook version less then 0.2 have ### Response: Having vulnarability PVE-2022-51463 Advisory: Django-js-error-hook 0.2 adds CSRF protection by default.
https://github.com/jojax/django-js-error-hook/commit/1d524883b6bcc1e4a6a4bc580c87dfd326828dc9 | what vulnarability does django-js-error-hook version less then 0.2 have | |
Having vulnarability CVE-2019-15486 Advisory: django-js-reverse (aka Django JS Reverse) before 0.9.1 has XSS via js_reverse_inline. See: CVE-2019-15486. | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-js-reverse version less then 0.9.1 have ### Response: Having vulnarability CVE-2019-15486 Advisory: django-js-reverse (aka Django JS Reverse) before 0.9.1 has XSS via js_reverse_inline. See: CVE-2019-15486. | what vulnarability does django-js-reverse version less then 0.9.1 have | |
Having vulnarability PVE-2024-66924 Advisory: Django-json-widget version 2.0.0 introduces measures to prevent HTML injection by ensuring JSON inputs are safely handled, thus enhancing the security against unsafe content injection vulnerabilities.
https://github.com/jmrivas86/django-json-widget/pull/64/commits/bbe84655c3df2b32aade1997953dd06bffcb489e | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-json-widget version less then 2.0.0 have ### Response: Having vulnarability PVE-2024-66924 Advisory: Django-json-widget version 2.0.0 introduces measures to prevent HTML injection by ensuring JSON inputs are safely handled, thus enhancing the security against unsafe content injection vulnerabilities.
https://github.com/jmrivas86/django-json-widget/pull/64/commits/bbe84655c3df2b32aade1997953dd06bffcb489e | what vulnarability does django-json-widget version less then 2.0.0 have | |
Having vulnarability PVE-2022-49361 Advisory: Django-jsonform 2.10.1 includes a fix for a high severity vulnerability (XSS) in the admin form.
https://github.com/bhch/django-jsonform/security/advisories/GHSA-x9jp-4w8m-4f3c | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-jsonform version less then 2.10.1 have ### Response: Having vulnarability PVE-2022-49361 Advisory: Django-jsonform 2.10.1 includes a fix for a high severity vulnerability (XSS) in the admin form.
https://github.com/bhch/django-jsonform/security/advisories/GHSA-x9jp-4w8m-4f3c | what vulnarability does django-jsonform version less then 2.10.1 have | |
Having vulnarability CVE-2021-20270 Advisory: Django-kaio 0.15.0 updates its dependency 'pygments' to v2.7.4 to include security fixes. | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-kaio version less then 0.15.0 have ### Response: Having vulnarability CVE-2021-20270 Advisory: Django-kaio 0.15.0 updates its dependency 'pygments' to v2.7.4 to include security fixes. | what vulnarability does django-kaio version less then 0.15.0 have | |
Having vulnarability PVE-2021-25770 Advisory: Django-lazysignup before 0.4.0 fixes a security issue: Generated usernames are now based on the session key, rather than actually being the session key. This is to avoid a potential security issue where an app might simply display a username, giving away a significant part of the user's session key. The username is now generated from a SHA1 hash of the session key. This change means that existing generated users will become invalid.
https://github.com/danfairs/django-lazysignup/commit/ea27d50ea222063de81f005565dfbb7f83d8759f | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-lazysignup version less then 0.4.0 have ### Response: Having vulnarability PVE-2021-25770 Advisory: Django-lazysignup before 0.4.0 fixes a security issue: Generated usernames are now based on the session key, rather than actually being the session key. This is to avoid a potential security issue where an app might simply display a username, giving away a significant part of the user's session key. The username is now generated from a SHA1 hash of the session key. This change means that existing generated users will become invalid.
https://github.com/danfairs/django-lazysignup/commit/ea27d50ea222063de81f005565dfbb7f83d8759f | what vulnarability does django-lazysignup version less then 0.4.0 have | |
Having vulnarability PVE-2021-25772 Advisory: Django-lfs before 0.6.9 protects all manage methods. Before, they could be reached from outside by anonymous users.
https://github.com/diefenbach/django-lfs/commit/5bfa41d2b27e7d23967e4cf9b25107f9da389470 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-lfs version less then 0.6.9 have ### Response: Having vulnarability PVE-2021-25772 Advisory: Django-lfs before 0.6.9 protects all manage methods. Before, they could be reached from outside by anonymous users.
https://github.com/diefenbach/django-lfs/commit/5bfa41d2b27e7d23967e4cf9b25107f9da389470 | what vulnarability does django-lfs version less then 0.6.9 have | |
Having vulnarability CVE-2021-25288 Advisory: Django-loci 0.4.3 updates its dependency 'Pillow' to versions ~=8.2.0 to include security fixes. | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-loci version less then 0.4.3 have ### Response: Having vulnarability CVE-2021-25288 Advisory: Django-loci 0.4.3 updates its dependency 'Pillow' to versions ~=8.2.0 to include security fixes. | what vulnarability does django-loci version less then 0.4.3 have | |
Having vulnarability PVE-2021-41829 Advisory: Django-magiclink 1.0.4 adds csrf_protect decorator for POST requests by default to improve security. | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-magiclink version less then 1.0.4 have ### Response: Having vulnarability PVE-2021-41829 Advisory: Django-magiclink 1.0.4 adds csrf_protect decorator for POST requests by default to improve security. | what vulnarability does django-magiclink version less then 1.0.4 have | |
Having vulnarability PVE-2021-37171 Advisory: Django-mail-auth before 0.1.3 uses a session hash always identical and predictable for an attacker.
https://github.com/codingjoe/django-mail-auth/pull/1 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-mail-auth version less then 0.1.3 have ### Response: Having vulnarability PVE-2021-37171 Advisory: Django-mail-auth before 0.1.3 uses a session hash always identical and predictable for an attacker.
https://github.com/codingjoe/django-mail-auth/pull/1 | what vulnarability does django-mail-auth version less then 0.1.3 have | |
Having vulnarability CVE-2017-16764 Advisory: An exploitable vulnerability exists in the YAML parsing functionality in the read_yaml_file method in io_utils.py in django_make_app 0.1.3. A YAML parser can execute arbitrary Python commands resulting in command execution. An attacker can insert Python into loaded YAML to trigger this vulnerability. | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-make-app version less then 0.1.3 have ### Response: Having vulnarability CVE-2017-16764 Advisory: An exploitable vulnerability exists in the YAML parsing functionality in the read_yaml_file method in io_utils.py in django_make_app 0.1.3. A YAML parser can execute arbitrary Python commands resulting in command execution. An attacker can insert Python into loaded YAML to trigger this vulnerability. | what vulnarability does django-make-app version less then 0.1.3 have | |
Having vulnarability PVE-2021-38936 Advisory: Django-mapstore-adapter 1.0.4 fixes unescaped "ms2_config" which may cause JS injection.
https://github.com/GeoNode/django-mapstore-adapter/commit/57e01b55567672961f8c6b7ca3b9dec18cc425b9 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-mapstore-adapter version less then 1.0.4 have ### Response: Having vulnarability PVE-2021-38936 Advisory: Django-mapstore-adapter 1.0.4 fixes unescaped "ms2_config" which may cause JS injection.
https://github.com/GeoNode/django-mapstore-adapter/commit/57e01b55567672961f8c6b7ca3b9dec18cc425b9 | what vulnarability does django-mapstore-adapter version less then 1.0.4 have | |
Having vulnarability CVE-2024-2319 Advisory: Cross-Site Scripting (XSS) vulnerability in the Django MarkdownX project, affecting version 4.0.2. An attacker could store a specially crafted JavaScript payload in the upload functionality due to lack of proper sanitisation of JavaScript elements. See CVE-2024-2319. | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-markdownx version less then equal to 4.0.2 have ### Response: Having vulnarability CVE-2024-2319 Advisory: Cross-Site Scripting (XSS) vulnerability in the Django MarkdownX project, affecting version 4.0.2. An attacker could store a specially crafted JavaScript payload in the upload functionality due to lack of proper sanitisation of JavaScript elements. See CVE-2024-2319. | what vulnarability does django-markdownx version less then equal to 4.0.2 have | |
Having vulnarability PVE-2022-52542 Advisory: Django-markers 1.4.0 fixes a XSS vulnerability in error messages.
https://github.com/danielquinn/django-markers/commit/c0e27b36acb8ff3afba280556a980a7aff574263 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-markers version less then 1.4.0 have ### Response: Having vulnarability PVE-2022-52542 Advisory: Django-markers 1.4.0 fixes a XSS vulnerability in error messages.
https://github.com/danielquinn/django-markers/commit/c0e27b36acb8ff3afba280556a980a7aff574263 | what vulnarability does django-markers version less then 1.4.0 have | |
Having vulnarability CVE-2015-0846 Advisory: django-markupfield before 1.3.2 uses the default docutils RESTRUCTUREDTEXT_FILTER_SETTINGS settings, which allows remote attackers to include and read arbitrary files via unspecified vectors. | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-markupfield version less then 1.3.2 have ### Response: Having vulnarability CVE-2015-0846 Advisory: django-markupfield before 1.3.2 uses the default docutils RESTRUCTUREDTEXT_FILTER_SETTINGS settings, which allows remote attackers to include and read arbitrary files via unspecified vectors. | what vulnarability does django-markupfield version less then 1.3.2 have | |
Having vulnarability PVE-2021-25775 Advisory: Django-material 0.9.0 fixes a XSS vulnerability in input fields.
https://github.com/viewflow/django-material/issues/139 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-material version less then 0.9.0 have ### Response: Having vulnarability PVE-2021-25775 Advisory: Django-material 0.9.0 fixes a XSS vulnerability in input fields.
https://github.com/viewflow/django-material/issues/139 | what vulnarability does django-material version less then 0.9.0 have | |
Having vulnarability CVE-2022-42731 Advisory: Django-mfa2 2.5.1 and 2.6.1 include a fix for CVE-2022-42731: mfa/FIDO2.py in django-mfa2 before 2.5.1 and 2.6.x before 2.6.1 allows a replay attack that could be used to register another device for a user. The device registration challenge is not invalidated after usage. | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-mfa2 version less then 2.5.1,greather then equal to 2.6.0rc1,less then 2.6.1 have ### Response: Having vulnarability CVE-2022-42731 Advisory: Django-mfa2 2.5.1 and 2.6.1 include a fix for CVE-2022-42731: mfa/FIDO2.py in django-mfa2 before 2.5.1 and 2.6.x before 2.6.1 allows a replay attack that could be used to register another device for a user. The device registration challenge is not invalidated after usage. | what vulnarability does django-mfa2 version less then 2.5.1,greather then equal to 2.6.0rc1,less then 2.6.1 have | |
Having vulnarability CVE-2022-24857 Advisory: Django-mfa3 0.5.0 includes a fix for CVE-2022-24857: Django-mfa3 is a library that implements multi factor authentication for the django web framework. It achieves this by modifying the regular login view. Django however has a second login view for its admin area. This second login view was not modified, so the multi factor authentication can be bypassed. Users are affected if they have activated both django-mfa3 (< 0.5.0) and django.contrib.admin and have not taken any other measures to prevent users from accessing the admin login view. It is possible to work around the issue by overwriting the admin login route, e.g. by adding the following URL definition before the admin routes: url('admin/login/', lambda request: redirect(settings.LOGIN_URL).
https://github.com/xi/django-mfa3/security/advisories/GHSA-3r7g-wrpr-j5g4 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-mfa3 version less then 0.5.0 have ### Response: Having vulnarability CVE-2022-24857 Advisory: Django-mfa3 0.5.0 includes a fix for CVE-2022-24857: Django-mfa3 is a library that implements multi factor authentication for the django web framework. It achieves this by modifying the regular login view. Django however has a second login view for its admin area. This second login view was not modified, so the multi factor authentication can be bypassed. Users are affected if they have activated both django-mfa3 (< 0.5.0) and django.contrib.admin and have not taken any other measures to prevent users from accessing the admin login view. It is possible to work around the issue by overwriting the admin login route, e.g. by adding the following URL definition before the admin routes: url('admin/login/', lambda request: redirect(settings.LOGIN_URL).
https://github.com/xi/django-mfa3/security/advisories/GHSA-3r7g-wrpr-j5g4 | what vulnarability does django-mfa3 version less then 0.5.0 have | |
Having vulnarability PVE-2021-34991 Advisory: Django-modern-rpc before 0.8.1 isn't correctly checking the authentication backend when executing 'system.multicall()'.
https://github.com/alorence/django-modern-rpc/commit/88fb4c40ce1a6346d7a22f9eafbdc58a4b7b3a96 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-modern-rpc version less then 0.8.1 have ### Response: Having vulnarability PVE-2021-34991 Advisory: Django-modern-rpc before 0.8.1 isn't correctly checking the authentication backend when executing 'system.multicall()'.
https://github.com/alorence/django-modern-rpc/commit/88fb4c40ce1a6346d7a22f9eafbdc58a4b7b3a96 | what vulnarability does django-modern-rpc version less then 0.8.1 have | |
Having vulnarability CVE-2015-0219 Advisory: Django-mptt 0.8.0 drops support for Django versions <1.8. They no longer receive security patches. | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-mptt version less then 0.8.0 have ### Response: Having vulnarability CVE-2015-0219 Advisory: Django-mptt 0.8.0 drops support for Django versions <1.8. They no longer receive security patches. | what vulnarability does django-mptt version less then 0.8.0 have | |
Having vulnarability CVE-2024-26164 Advisory: Microsoft Django Backend for SQL Server Remote Code Execution Vulnerability See CVE-2024-26164. | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-mssql-backend version less then 1.4.1 have ### Response: Having vulnarability CVE-2024-26164 Advisory: Microsoft Django Backend for SQL Server Remote Code Execution Vulnerability See CVE-2024-26164. | what vulnarability does django-mssql-backend version less then 1.4.1 have | |
Having vulnarability CVE-2018-16984 Advisory: Django-music-publisher 18.9.1 updates its dependency 'Django' to v2.1.2 to include a security fix. | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-music-publisher version less then 18.9.1 have ### Response: Having vulnarability CVE-2018-16984 Advisory: Django-music-publisher 18.9.1 updates its dependency 'Django' to v2.1.2 to include a security fix. | what vulnarability does django-music-publisher version less then 18.9.1 have | |
Having vulnarability CVE-2019-6975 Advisory: Django-nameko-standalone 1.3.2 updates its Django version to 1.11.27 to include security fixes. | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-nameko-standalone version less then 1.3.2 have ### Response: Having vulnarability CVE-2019-6975 Advisory: Django-nameko-standalone 1.3.2 updates its Django version to 1.11.27 to include security fixes. | what vulnarability does django-nameko-standalone version less then 1.3.2 have | |
Having vulnarability CVE-2022-32996 Advisory: Django-navbar-client v0.9.50 to v1.0.1 was discovered to contain a code execution backdoor via the request package. This vulnerability allows attackers to access sensitive user information and digital currency keys, as well as escalate privileges. | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-navbar-client version greather then equal to 0.9.50,less then equal to 1.0.1 have ### Response: Having vulnarability CVE-2022-32996 Advisory: Django-navbar-client v0.9.50 to v1.0.1 was discovered to contain a code execution backdoor via the request package. This vulnerability allows attackers to access sensitive user information and digital currency keys, as well as escalate privileges. | what vulnarability does django-navbar-client version greather then equal to 0.9.50,less then equal to 1.0.1 have | |
Having vulnarability PVE-2021-36318 Advisory: django-newsletter before 0.7 allowed a user to subscribe others to the newsletter without authorization.
https://github.com/jazzband/django-newsletter/commit/bea5a5100cc40717995dafc65ff011bc76696ebd | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-newsletter version less then 0.7 have ### Response: Having vulnarability PVE-2021-36318 Advisory: django-newsletter before 0.7 allowed a user to subscribe others to the newsletter without authorization.
https://github.com/jazzband/django-newsletter/commit/bea5a5100cc40717995dafc65ff011bc76696ebd | what vulnarability does django-newsletter version less then 0.7 have | |
Having vulnarability PVE-2021-25776 Advisory: Django-ninecms before 0.4.5b has a unknown security issue in its url configuration. | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-ninecms version less then 0.4.5b have ### Response: Having vulnarability PVE-2021-25776 Advisory: Django-ninecms before 0.4.5b has a unknown security issue in its url configuration. | what vulnarability does django-ninecms version less then 0.4.5b have | |
Having vulnarability CVE-2019-10682 Advisory: django-nopassword before 5.0.0 stores cleartext secrets in the database. See: CVE-2019-10682. | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-nopassword version less then 5.0.0 have ### Response: Having vulnarability CVE-2019-10682 Advisory: django-nopassword before 5.0.0 stores cleartext secrets in the database. See: CVE-2019-10682. | what vulnarability does django-nopassword version less then 5.0.0 have | |
Having vulnarability PVE-2021-39609 Advisory: Django-oauth-toolkit 0.8.0 includes fixes for various vulnerabilities on 'Basic' authentication.
https://github.com/jazzband/django-oauth-toolkit/commit/83367ffe5ad1046f5a5338537a8655cb1c16400d | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-oauth-toolkit version less then 0.8.0 have ### Response: Having vulnarability PVE-2021-39609 Advisory: Django-oauth-toolkit 0.8.0 includes fixes for various vulnerabilities on 'Basic' authentication.
https://github.com/jazzband/django-oauth-toolkit/commit/83367ffe5ad1046f5a5338537a8655cb1c16400d | what vulnarability does django-oauth-toolkit version less then 0.8.0 have | |
Having vulnarability CVE-2018-14574 Advisory: Django-orghierarchy 0.1.13 updates its dependency 'Django' to v1.11.15 to include a security fix. | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-orghierarchy version less then 0.1.13 have ### Response: Having vulnarability CVE-2018-14574 Advisory: Django-orghierarchy 0.1.13 updates its dependency 'Django' to v1.11.15 to include a security fix. | what vulnarability does django-orghierarchy version less then 0.1.13 have | |
Having vulnarability PVE-2021-41899 Advisory: Django-pagetree version 1.0.4 adds csrf_tokens to several forms where it was missing. | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-pagetree version less then 1.0.4 have ### Response: Having vulnarability PVE-2021-41899 Advisory: Django-pagetree version 1.0.4 adds csrf_tokens to several forms where it was missing. | what vulnarability does django-pagetree version less then 1.0.4 have | |
Having vulnarability CVE-2019-13122 Advisory: A Cross Site Scripting (XSS) vulnerability exists in the template tag used to render message ids in Patchwork v1.1 through v2.1.x. This allows an attacker to insert JavaScript or HTML into the patch detail page via an email sent to a mailing list consumed by Patchwork. This affects the function msgid in templatetags/patch.py. Patchwork versions v2.1.4 and v2.0.4 will contain the fix. | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-patchwork version greather then equal to 1.1,less then 2.0.4,greather then equal to 2.1.0,less then 2.1.4,equal to 2.1.0:rc1,equal to 2.1.0:rc2 have ### Response: Having vulnarability CVE-2019-13122 Advisory: A Cross Site Scripting (XSS) vulnerability exists in the template tag used to render message ids in Patchwork v1.1 through v2.1.x. This allows an attacker to insert JavaScript or HTML into the patch detail page via an email sent to a mailing list consumed by Patchwork. This affects the function msgid in templatetags/patch.py. Patchwork versions v2.1.4 and v2.0.4 will contain the fix. | what vulnarability does django-patchwork version greather then equal to 1.1,less then 2.0.4,greather then equal to 2.1.0,less then 2.1.4,equal to 2.1.0:rc1,equal to 2.1.0:rc2 have | |
Having vulnarability CVE-2020-1747 Advisory: Django-perms-provisioner 0.0.4 updates PyYAML to v5.3.1 to include security fixes. | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-perms-provisioner version less then 0.0.4 have ### Response: Having vulnarability CVE-2020-1747 Advisory: Django-perms-provisioner 0.0.4 updates PyYAML to v5.3.1 to include security fixes. | what vulnarability does django-perms-provisioner version less then 0.0.4 have | |
Having vulnarability PVE-2023-61662 Advisory: Django-pgbulk 2.0.0 updates 'pgbulk.upsert' to no longer support the 'return_untouched` argument, as it had race conditions. | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-pgbulk version less then 2.0.0 have ### Response: Having vulnarability PVE-2023-61662 Advisory: Django-pgbulk 2.0.0 updates 'pgbulk.upsert' to no longer support the 'return_untouched` argument, as it had race conditions. | what vulnarability does django-pgbulk version less then 2.0.0 have | |
Having vulnarability PVE-2023-53875 Advisory: Django-pghistory 2.6.0 escapes all context data to avoid SQL injection attacks.
https://github.com/Opus10/django-pghistory/commit/a5380fa85745731c6bc749f0e453ab66314c0bc7 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-pghistory version less then 2.6.0 have ### Response: Having vulnarability PVE-2023-53875 Advisory: Django-pghistory 2.6.0 escapes all context data to avoid SQL injection attacks.
https://github.com/Opus10/django-pghistory/commit/a5380fa85745731c6bc749f0e453ab66314c0bc7 | what vulnarability does django-pghistory version less then 2.6.0 have | |
Having vulnarability CVE-2022-4526 Advisory: A vulnerability was found in django-photologue up to 3.15.1 and classified as problematic. Affected by this issue is some unknown functionality of the file photologue/templates/photologue/photo_detail.html of the component Default Template Handler. The manipulation of the argument object.caption leads to cross site scripting. The attack may be launched remotely.
https://github.com/richardbarran/django-photologue/issues/223 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-photologue version less then equal to 3.15.1 have ### Response: Having vulnarability CVE-2022-4526 Advisory: A vulnerability was found in django-photologue up to 3.15.1 and classified as problematic. Affected by this issue is some unknown functionality of the file photologue/templates/photologue/photo_detail.html of the component Default Template Handler. The manipulation of the argument object.caption leads to cross site scripting. The attack may be launched remotely.
https://github.com/richardbarran/django-photologue/issues/223 | what vulnarability does django-photologue version less then equal to 3.15.1 have | |
Having vulnarability CVE-2011-4103 Advisory: emitters.py in Django Piston before 0.2.3 and 0.2.x before 0.2.2.1 does not properly deserialize YAML data, which allows remote attackers to execute arbitrary Python code via vectors related to the yaml.load method. | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-piston version less then 0.2.3 have ### Response: Having vulnarability CVE-2011-4103 Advisory: emitters.py in Django Piston before 0.2.3 and 0.2.x before 0.2.2.1 does not properly deserialize YAML data, which allows remote attackers to execute arbitrary Python code via vectors related to the yaml.load method. | what vulnarability does django-piston version less then 0.2.3 have | |
Having vulnarability PVE-2021-25778 Advisory: Django-pluggable-filebrowser 3.4.2 fixes a XSS vulnerability.
https://github.com/sehmaschine/django-filebrowser/pull/88 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-pluggable-filebrowser version less then 3.4.2 have ### Response: Having vulnarability PVE-2021-25778 Advisory: Django-pluggable-filebrowser 3.4.2 fixes a XSS vulnerability.
https://github.com/sehmaschine/django-filebrowser/pull/88 | what vulnarability does django-pluggable-filebrowser version less then 3.4.2 have | |
Having vulnarability PVE-2021-36667 Advisory: Django-postman 3.6.2 fixes an open redirect vulnerability within the "next" parameter.
https://bitbucket.org/psam/django-postman/issues/101/open-redirect-vulnerability-within-the | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-postman version less then 3.6.2 have ### Response: Having vulnarability PVE-2021-36667 Advisory: Django-postman 3.6.2 fixes an open redirect vulnerability within the "next" parameter.
https://bitbucket.org/psam/django-postman/issues/101/open-redirect-vulnerability-within-the | what vulnarability does django-postman version less then 3.6.2 have | |
Having vulnarability PVE-2021-25779 Advisory: Django-python3-ldap 0.9.5 fixes a security vulnerability where username and password could be transmitted in plain text before starting TLS.
https://github.com/etianen/django-python3-ldap/commit/a250194e2911e270a90b0eec2251343040a75ece | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-python3-ldap version less then 0.9.5 have ### Response: Having vulnarability PVE-2021-25779 Advisory: Django-python3-ldap 0.9.5 fixes a security vulnerability where username and password could be transmitted in plain text before starting TLS.
https://github.com/etianen/django-python3-ldap/commit/a250194e2911e270a90b0eec2251343040a75ece | what vulnarability does django-python3-ldap version less then 0.9.5 have | |
Having vulnarability PVE-2021-25781 Advisory: Django-rated 1.1.2 sets 'X-Forwarded-For=False' by default. X-Forwarded-For HTTP header should not be used for any Access Control List (ACL) checks because it can be spoofed by attackers.
https://github.com/funkybob/django-rated/commit/bb0766470ab0a30ab374b291dded6212fa1285e2 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-rated version less then 1.1.2 have ### Response: Having vulnarability PVE-2021-25781 Advisory: Django-rated 1.1.2 sets 'X-Forwarded-For=False' by default. X-Forwarded-For HTTP header should not be used for any Access Control List (ACL) checks because it can be spoofed by attackers.
https://github.com/funkybob/django-rated/commit/bb0766470ab0a30ab374b291dded6212fa1285e2 | what vulnarability does django-rated version less then 1.1.2 have | |
Having vulnarability PVE-2023-52696 Advisory: Django-react-templatetags 6.0.1 includes a fix for a XSS vulnerability.
https://github.com/Frojd/django-react-templatetags/commit/62933728f6fb4b3ca31cf67dc1f673ca38b25286 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-react-templatetags version less then 6.0.1 have ### Response: Having vulnarability PVE-2023-52696 Advisory: Django-react-templatetags 6.0.1 includes a fix for a XSS vulnerability.
https://github.com/Frojd/django-react-templatetags/commit/62933728f6fb4b3ca31cf67dc1f673ca38b25286 | what vulnarability does django-react-templatetags version less then 6.0.1 have | |
Having vulnarability PVE-2021-36431 Advisory: django-registration before 1.7 leaked password reset token through the Referer
header.
https://github.com/macropin/django-registration/commit/3a2e0182ff92cc8ce39a932e463cbac37e485afa | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-registration version less then 1.7 have ### Response: Having vulnarability PVE-2021-36431 Advisory: django-registration before 1.7 leaked password reset token through the Referer
header.
https://github.com/macropin/django-registration/commit/3a2e0182ff92cc8ce39a932e463cbac37e485afa | what vulnarability does django-registration version less then 1.7 have | |
Having vulnarability PVE-2021-35199 Advisory: django-registration-redux before 1.7 leaks password reset tokens through the Referer header. For more info, see: https://github.com/macropin/django-registration/pull/268 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-registration-redux version less then 1.7 have ### Response: Having vulnarability PVE-2021-35199 Advisory: django-registration-redux before 1.7 leaks password reset tokens through the Referer header. For more info, see: https://github.com/macropin/django-registration/pull/268 | what vulnarability does django-registration-redux version less then 1.7 have | |
Having vulnarability PVE-2021-25782 Advisory: Django-relatives before 0.3.0 is vulnerable to XSS in html tags.
https://github.com/treyhunner/django-relatives/commit/6410ae4695389cb377ce23d35883d8b70b789deb | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-relatives version less then 0.3.0 have ### Response: Having vulnarability PVE-2021-25782 Advisory: Django-relatives before 0.3.0 is vulnerable to XSS in html tags.
https://github.com/treyhunner/django-relatives/commit/6410ae4695389cb377ce23d35883d8b70b789deb | what vulnarability does django-relatives version less then 0.3.0 have | |
Having vulnarability CVE-2020-25626 Advisory: Django-rest-framework 3.11.2 includes a fix for CVE-2020-25626: When using the browseable API viewer, Django REST Framework fails to properly escape certain strings that can come from user input. This allows a user who can control those strings to inject malicious "script" tags, leading to a cross-site-scripting (XSS) vulnerability. | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-rest-framework version less then 3.11.2 have ### Response: Having vulnarability CVE-2020-25626 Advisory: Django-rest-framework 3.11.2 includes a fix for CVE-2020-25626: When using the browseable API viewer, Django REST Framework fails to properly escape certain strings that can come from user input. This allows a user who can control those strings to inject malicious "script" tags, leading to a cross-site-scripting (XSS) vulnerability. | what vulnarability does django-rest-framework version less then 3.11.2 have | |
Having vulnarability CVE-2019-13177 Advisory: Django-rest-registration 0.5.0 includes a fix for CVE-2019-13177: verification.py in django-rest-registration before 0.5.0 relies on a static string for signatures (i.e., the Django Signing API is misused), which allows remote attackers to spoof the verification process. This occurs because incorrect code refactoring led to calling a security-critical function with an incorrect argument. | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-rest-registration version less then 0.5.0 have ### Response: Having vulnarability CVE-2019-13177 Advisory: Django-rest-registration 0.5.0 includes a fix for CVE-2019-13177: verification.py in django-rest-registration before 0.5.0 relies on a static string for signatures (i.e., the Django Signing API is misused), which allows remote attackers to spoof the verification process. This occurs because incorrect code refactoring led to calling a security-critical function with an incorrect argument. | what vulnarability does django-rest-registration version less then 0.5.0 have | |
Having vulnarability PVE-2021-25783 Advisory: Django-revproxy 0.9.6 fixes a security issue that allowed remote-user header injection.
https://github.com/jazzband/django-revproxy/commit/0ce23b632fc7c1b4cb5f5e03077b45e6ece802e6 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-revproxy version less then 0.9.6 have ### Response: Having vulnarability PVE-2021-25783 Advisory: Django-revproxy 0.9.6 fixes a security issue that allowed remote-user header injection.
https://github.com/jazzband/django-revproxy/commit/0ce23b632fc7c1b4cb5f5e03077b45e6ece802e6 | what vulnarability does django-revproxy version less then 0.9.6 have | |
Having vulnarability PVE-2023-58913 Advisory: Django-rq-scheduler 2023.6.1 includes a fix for a HTML injection vulnerability.
https://github.com/dsoftwareinc/django-rq-scheduler/commit/51a47230babc583ebd8230c40bc264af215d404e | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-rq-scheduler version less then 2023.6.1 have ### Response: Having vulnarability PVE-2023-58913 Advisory: Django-rq-scheduler 2023.6.1 includes a fix for a HTML injection vulnerability.
https://github.com/dsoftwareinc/django-rq-scheduler/commit/51a47230babc583ebd8230c40bc264af215d404e | what vulnarability does django-rq-scheduler version less then 2023.6.1 have | |
Having vulnarability CVE-2022-24840 Advisory: Django-s3file 5.5.1 includes a fix for CVE-2022-24840: In versions prior to 5.5.1 it was possible to traverse the entire AWS S3 bucket and in most cases to access or delete files. If the 'AWS_LOCATION' setting was set, traversal was limited to that location only. The issue was discovered by the maintainer. There were no reports of the vulnerability being known to or exploited by a third party, prior to the release of the patch. | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-s3file version less then 5.5.1 have ### Response: Having vulnarability CVE-2022-24840 Advisory: Django-s3file 5.5.1 includes a fix for CVE-2022-24840: In versions prior to 5.5.1 it was possible to traverse the entire AWS S3 bucket and in most cases to access or delete files. If the 'AWS_LOCATION' setting was set, traversal was limited to that location only. The issue was discovered by the maintainer. There were no reports of the vulnerability being known to or exploited by a third party, prior to the release of the patch. | what vulnarability does django-s3file version less then 5.5.1 have | |
Having vulnarability PVE-2021-25785 Advisory: Django-safedelete 0.3.3 contains a security fix that prevents an XSS attack in the admin interface.
https://github.com/makinacorpus/django-safedelete/commit/317c548c9d53e8983bb9a361c02f658f635ac13e | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-safedelete version less then 0.3.3 have ### Response: Having vulnarability PVE-2021-25785 Advisory: Django-safedelete 0.3.3 contains a security fix that prevents an XSS attack in the admin interface.
https://github.com/makinacorpus/django-safedelete/commit/317c548c9d53e8983bb9a361c02f658f635ac13e | what vulnarability does django-safedelete version less then 0.3.3 have | |
Having vulnarability PVE-2021-41101 Advisory: Django-sage-painless 1.10.2 stores sensitive data as env variables to avoid information exposure.
https://github.com/sageteam-org/django-sage-painless/commit/b901519e5e8d371ee51166fff56000c8478f7268 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-sage-painless version less then 1.10.2 have ### Response: Having vulnarability PVE-2021-41101 Advisory: Django-sage-painless 1.10.2 stores sensitive data as env variables to avoid information exposure.
https://github.com/sageteam-org/django-sage-painless/commit/b901519e5e8d371ee51166fff56000c8478f7268 | what vulnarability does django-sage-painless version less then 1.10.2 have | |
Having vulnarability CVE-2014-3566 Advisory: Django-salesforce 0.6.3 defaults to use the most secure TLS version (TLSv1.1).
https://github.com/django-salesforce/django-salesforce/commit/78cfc735195ef0cc45d0709f31abf26b5570be83 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-salesforce version less then 0.6.3 have ### Response: Having vulnarability CVE-2014-3566 Advisory: Django-salesforce 0.6.3 defaults to use the most secure TLS version (TLSv1.1).
https://github.com/django-salesforce/django-salesforce/commit/78cfc735195ef0cc45d0709f31abf26b5570be83 | what vulnarability does django-salesforce version less then 0.6.3 have | |
Having vulnarability CVE-2022-23833 Advisory: Django-secured-fields 0.3.1 updates its dependency 'django' to v4.0.2 to include security fixes. | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-secured-fields version less then 0.3.1 have ### Response: Having vulnarability CVE-2022-23833 Advisory: Django-secured-fields 0.3.1 updates its dependency 'django' to v4.0.2 to include security fixes. | what vulnarability does django-secured-fields version less then 0.3.1 have | |
Having vulnarability PVE-2021-25787 Advisory: Django-select2 5.7.0 contains a security fix that allows a `field_id` to only be used for the intended JSON endpoint.
https://github.com/applegrew/django-select2/commit/4a1b83ad1e9b2523961a0f23706c70b01683494f | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-select2 version less then 5.7.0 have ### Response: Having vulnarability PVE-2021-25787 Advisory: Django-select2 5.7.0 contains a security fix that allows a `field_id` to only be used for the intended JSON endpoint.
https://github.com/applegrew/django-select2/commit/4a1b83ad1e9b2523961a0f23706c70b01683494f | what vulnarability does django-select2 version less then 5.7.0 have | |
Having vulnarability PVE-2021-25788 Advisory: Django-selectable 0.5.2 fixes a XSS flaw with lookup "get_item_*" methods.
https://github.com/mlavin/django-selectable/issues/63 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-selectable version less then 0.5.2 have ### Response: Having vulnarability PVE-2021-25788 Advisory: Django-selectable 0.5.2 fixes a XSS flaw with lookup "get_item_*" methods.
https://github.com/mlavin/django-selectable/issues/63 | what vulnarability does django-selectable version less then 0.5.2 have | |
Having vulnarability PVE-2023-55171 Advisory: Django-sendfile2 0.6.0 includes a fix for a path traversal vulnerability.
https://github.com/moggers87/django-sendfile2/security/advisories/GHSA-6r3c-8xf3-ggrr | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-sendfile2 version less then 0.6.0 have ### Response: Having vulnarability PVE-2023-55171 Advisory: Django-sendfile2 0.6.0 includes a fix for a path traversal vulnerability.
https://github.com/moggers87/django-sendfile2/security/advisories/GHSA-6r3c-8xf3-ggrr | what vulnarability does django-sendfile2 version less then 0.6.0 have | |
Having vulnarability PVE-2021-34982 Advisory: django-server is a package affected by pytosquatting: http://www.nbu.gov.sk/skcsirt-sa-20170909-pypi/ | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-server version greather then 0,less then 0 have ### Response: Having vulnarability PVE-2021-34982 Advisory: django-server is a package affected by pytosquatting: http://www.nbu.gov.sk/skcsirt-sa-20170909-pypi/ | what vulnarability does django-server version greather then 0,less then 0 have | |
Having vulnarability CVE-2023-33185 Advisory: Django-SES 3.5.0 includes a fix for CVE-2023-33185: The django_ses library implements a mail backend for Django using AWS Simple Email Service. The library exports the 'SESEventWebhookView class' intended to receive signed requests from AWS to handle email bounces, subscriptions, etc. These requests are signed by AWS and are verified by django_ses, however the verification of this signature was found to be flawed as it allowed users to specify arbitrary public certificates.
https://github.com/django-ses/django-ses/security/advisories/GHSA-qg36-9jxh-fj25 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-ses version less then 3.5.0 have ### Response: Having vulnarability CVE-2023-33185 Advisory: Django-SES 3.5.0 includes a fix for CVE-2023-33185: The django_ses library implements a mail backend for Django using AWS Simple Email Service. The library exports the 'SESEventWebhookView class' intended to receive signed requests from AWS to handle email bounces, subscriptions, etc. These requests are signed by AWS and are verified by django_ses, however the verification of this signature was found to be flawed as it allowed users to specify arbitrary public certificates.
https://github.com/django-ses/django-ses/security/advisories/GHSA-qg36-9jxh-fj25 | what vulnarability does django-ses version less then 3.5.0 have | |
Having vulnarability PVE-2021-25789 Advisory: Django-session-security 2.4.0 fixes a vulnerability when SESSION_EXPIRE_AT_BROWSER_CLOSE is off.
https://github.com/yourlabs/django-session-security/commit/52d531928fd5e84a1dceaf0bc8ca47beefc52523 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-session-security version less then 2.4.0 have ### Response: Having vulnarability PVE-2021-25789 Advisory: Django-session-security 2.4.0 fixes a vulnerability when SESSION_EXPIRE_AT_BROWSER_CLOSE is off.
https://github.com/yourlabs/django-session-security/commit/52d531928fd5e84a1dceaf0bc8ca47beefc52523 | what vulnarability does django-session-security version less then 2.4.0 have | |
Having vulnarability PVE-2022-49564 Advisory: Django-silk 3.2.0 masks sensitive data. Before, request bodies were stored as plain text in the database.
https://github.com/jazzband/django-silk/commit/04d8175eb6c712f5f713ebd0c3306d5e99dc2e15 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-silk version less then 3.0.2 have ### Response: Having vulnarability PVE-2022-49564 Advisory: Django-silk 3.2.0 masks sensitive data. Before, request bodies were stored as plain text in the database.
https://github.com/jazzband/django-silk/commit/04d8175eb6c712f5f713ebd0c3306d5e99dc2e15 | what vulnarability does django-silk version less then 3.0.2 have | |
Having vulnarability PVE-2021-38150 Advisory: Django-smart-lists 1.0.26 fixes a XSS vulnerability in the render_function.
https://github.com/plecto/django-smart-lists/commit/44314e51b371e01cd9bceb2e0ed6c8d75d7f87c3 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-smart-lists version less then 1.0.26 have ### Response: Having vulnarability PVE-2021-38150 Advisory: Django-smart-lists 1.0.26 fixes a XSS vulnerability in the render_function.
https://github.com/plecto/django-smart-lists/commit/44314e51b371e01cd9bceb2e0ed6c8d75d7f87c3 | what vulnarability does django-smart-lists version less then 1.0.26 have | |
Having vulnarability PVE-2021-34234 Advisory: Django-smart-selects before 1.5.0 allowed anybody to list arbitrary objects by tweaking URL parameters.
https://github.com/jazzband/django-smart-selects/releases/tag/1.5.0 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-smart-selects version less then 1.5.0 have ### Response: Having vulnarability PVE-2021-34234 Advisory: Django-smart-selects before 1.5.0 allowed anybody to list arbitrary objects by tweaking URL parameters.
https://github.com/jazzband/django-smart-selects/releases/tag/1.5.0 | what vulnarability does django-smart-selects version less then 1.5.0 have | |
Having vulnarability PVE-2021-25790 Advisory: Django-social-auth 0.7.2 fixes a security hole - redirects via the next param are now properly sanitized to disallow redirecting to external hosts. | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-social-auth version less then 0.7.2 have ### Response: Having vulnarability PVE-2021-25790 Advisory: Django-social-auth 0.7.2 fixes a security hole - redirects via the next param are now properly sanitized to disallow redirecting to external hosts. | what vulnarability does django-social-auth version less then 0.7.2 have | |
Having vulnarability PVE-2021-25791 Advisory: Django-social-auth3 0.3.3 fixes a security hole: redirects via the next param are now properly sanitized to disallow redirecting to external hosts.
https://github.com/omab/django-social-auth/commit/32a67fa2a751b59d6c775f8f201981c4a27b2610 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-social-auth3 version less then 0.3.3 have ### Response: Having vulnarability PVE-2021-25791 Advisory: Django-social-auth3 0.3.3 fixes a security hole: redirects via the next param are now properly sanitized to disallow redirecting to external hosts.
https://github.com/omab/django-social-auth/commit/32a67fa2a751b59d6c775f8f201981c4a27b2610 | what vulnarability does django-social-auth3 version less then 0.3.3 have | |
Having vulnarability PVE-2022-47773 Advisory: Django-spectator 11.7.0 strips out EXIF data from images uploaded as thumbnails.
https://github.com/philgyford/django-spectator/commit/370d1aa7109bddef206fe5e22aca3166a04a1d2a | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-spectator version less then 11.7.0 have ### Response: Having vulnarability PVE-2022-47773 Advisory: Django-spectator 11.7.0 strips out EXIF data from images uploaded as thumbnails.
https://github.com/philgyford/django-spectator/commit/370d1aa7109bddef206fe5e22aca3166a04a1d2a | what vulnarability does django-spectator version less then 11.7.0 have | |
Having vulnarability CVE-2022-0869 Advisory: django-spirit prior to version 0.12.3 is vulnerable to open redirect. In the /user/login endpoint, it doesn't check the value of the next parameter when the user is logged in and passes it directly to redirect which result to open redirect. This also affects /user/logout, /user/register, /user/login, /user/resend-activation. | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-spirit version greather then equal to 0,less then 0.12.3 have ### Response: Having vulnarability CVE-2022-0869 Advisory: django-spirit prior to version 0.12.3 is vulnerable to open redirect. In the /user/login endpoint, it doesn't check the value of the next parameter when the user is logged in and passes it directly to redirect which result to open redirect. This also affects /user/logout, /user/register, /user/login, /user/resend-activation. | what vulnarability does django-spirit version greather then equal to 0,less then 0.12.3 have | |
Having vulnarability PVE-2021-40482 Advisory: Django-sql-dashboard 0.14 fixes a security and permissions flaw, where users without the 'execute_sql' permission could still run custom queries by editing saved dashboards using the Django admin interface.
https://github.com/simonw/django-sql-dashboard/issues/94 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-sql-dashboard version less then 0.14 have ### Response: Having vulnarability PVE-2021-40482 Advisory: Django-sql-dashboard 0.14 fixes a security and permissions flaw, where users without the 'execute_sql' permission could still run custom queries by editing saved dashboards using the Django admin interface.
https://github.com/simonw/django-sql-dashboard/issues/94 | what vulnarability does django-sql-dashboard version less then 0.14 have | |
Having vulnarability PVE-2021-39445 Advisory: Django-sql-explorer before version 0.5 allows usage of query parameters to users with view permissions. This results in a potential for SQL injection.
https://github.com/groveco/django-sql-explorer/commit/ed491b70a02eb626826abc1230c3001a7d5ed489 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-sql-explorer version less then 0.5 have ### Response: Having vulnarability PVE-2021-39445 Advisory: Django-sql-explorer before version 0.5 allows usage of query parameters to users with view permissions. This results in a potential for SQL injection.
https://github.com/groveco/django-sql-explorer/commit/ed491b70a02eb626826abc1230c3001a7d5ed489 | what vulnarability does django-sql-explorer version less then 0.5 have | |
Having vulnarability PVE-2021-25793 Advisory: Django-sticky-uploads 0.2.0 fixes a security issue related to a client changing the upload url specified by the widget for the upload.
https://github.com/caktus/django-sticky-uploads/commit/81f4c1bf119b46c0716b0565c216e210960fc250 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-sticky-uploads version less then 0.2.0 have ### Response: Having vulnarability PVE-2021-25793 Advisory: Django-sticky-uploads 0.2.0 fixes a security issue related to a client changing the upload url specified by the widget for the upload.
https://github.com/caktus/django-sticky-uploads/commit/81f4c1bf119b46c0716b0565c216e210960fc250 | what vulnarability does django-sticky-uploads version less then 0.2.0 have | |
Having vulnarability PVE-2021-36434 Advisory: Django-storages before 1.7 have an insecure default ACL of 'public-read' in the 'S3BotoStorage' and 'S3Boto3Storage' backends .
https://github.com/jschneier/django-storages/commit/6ee6a739752923c60eaa1e82262c1d07208ec7f6 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-storages version less then 1.7 have ### Response: Having vulnarability PVE-2021-36434 Advisory: Django-storages before 1.7 have an insecure default ACL of 'public-read' in the 'S3BotoStorage' and 'S3Boto3Storage' backends .
https://github.com/jschneier/django-storages/commit/6ee6a739752923c60eaa1e82262c1d07208ec7f6 | what vulnarability does django-storages version less then 1.7 have | |
Having vulnarability PVE-2022-47921 Advisory: Django-su 0.6.0 makes sure all CSRF protection is enabled.
https://github.com/adamcharnock/django-su/commit/f75ea076577a824b0f81e35fc0c568a23a16cad2 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-su version less then 0.6.0 have ### Response: Having vulnarability PVE-2022-47921 Advisory: Django-su 0.6.0 makes sure all CSRF protection is enabled.
https://github.com/adamcharnock/django-su/commit/f75ea076577a824b0f81e35fc0c568a23a16cad2 | what vulnarability does django-su version less then 0.6.0 have | |
Having vulnarability CVE-2011-4104 Advisory: The from_yaml method in serializers.py in Django Tastypie before 0.9.10 does not properly deserialize YAML data, which allows remote attackers to execute arbitrary Python code via vectors related to the yaml.load method. | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-tastypie version less then 0.9.10 have ### Response: Having vulnarability CVE-2011-4104 Advisory: The from_yaml method in serializers.py in Django Tastypie before 0.9.10 does not properly deserialize YAML data, which allows remote attackers to execute arbitrary Python code via vectors related to the yaml.load method. | what vulnarability does django-tastypie version less then 0.9.10 have | |
Having vulnarability PVE-2022-49632 Advisory: Django-termsandconditions 2.0.10 fixes an open redirect vulnerability.
https://github.com/cyface/django-termsandconditions/commit/03396a1c2e0af95e12a45c5faef7e47a4b513e1a | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-termsandconditions version less then 2.0.10 have ### Response: Having vulnarability PVE-2022-49632 Advisory: Django-termsandconditions 2.0.10 fixes an open redirect vulnerability.
https://github.com/cyface/django-termsandconditions/commit/03396a1c2e0af95e12a45c5faef7e47a4b513e1a | what vulnarability does django-termsandconditions version less then 2.0.10 have | |
Having vulnarability CVE-2024-21910 Advisory: Django-tinymce 3.4.0 updates its NuGet dependency 'TinyMCE' to v5.10.1 to include a fix for a cross-site scripting vulnerability: a remote and unauthenticated attacker could introduce crafted image or link URLs that would result in the execution of arbitrary JavaScript in an editing user's browser. | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-tinymce version less then 3.4.0 have ### Response: Having vulnarability CVE-2024-21910 Advisory: Django-tinymce 3.4.0 updates its NuGet dependency 'TinyMCE' to v5.10.1 to include a fix for a cross-site scripting vulnerability: a remote and unauthenticated attacker could introduce crafted image or link URLs that would result in the execution of arbitrary JavaScript in an editing user's browser. | what vulnarability does django-tinymce version less then 3.4.0 have | |
Having vulnarability PVE-2024-64721 Advisory: Django-treenode 0.20.0 fixes an XSS vulnerability in `get_display_text` method. | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-treenode version less then 0.20.0 have ### Response: Having vulnarability PVE-2024-64721 Advisory: Django-treenode 0.20.0 fixes an XSS vulnerability in `get_display_text` method. | what vulnarability does django-treenode version less then 0.20.0 have | |
Having vulnarability PVE-2021-42899 Advisory: Django-trench 0.2.3 updates default backup codes settings to a more secure standard.
https://github.com/merixstudio/django-trench/pull/52 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-trench version less then 0.2.3 have ### Response: Having vulnarability PVE-2021-42899 Advisory: Django-trench 0.2.3 updates default backup codes settings to a more secure standard.
https://github.com/merixstudio/django-trench/pull/52 | what vulnarability does django-trench version less then 0.2.3 have | |
Having vulnarability CVE-2018-14574 Advisory: Django-triggers 2.0.13 updates its dependency 'Django' to v2.1.5 to include security fixes. | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-triggers version less then 2.0.13 have ### Response: Having vulnarability CVE-2018-14574 Advisory: Django-triggers 2.0.13 updates its dependency 'Django' to v2.1.5 to include security fixes. | what vulnarability does django-triggers version less then 2.0.13 have | |
Having vulnarability CVE-2020-15105 Advisory: Django Two-Factor Authentication before 1.12, stores the user's password in clear text in the user session (base64-encoded). The password is stored in the session when the user submits their username and password, and is removed once they complete authentication by entering a two-factor authentication code. This means that the password is stored in clear text in the session for an arbitrary amount of time, and potentially forever if the user begins the login process by entering their username and password and then leaves before entering their two-factor authentication code. The severity of this issue depends on which type of session storage you have configured: in the worst case, if you're using Django's default database session storage, then users' passwords are stored in clear text in your database. In the best case, if you're using Django's signed cookie session, then users' passwords are only stored in clear text within their browser's cookie store. In the common case of using Django's cache session store, the users' passwords are stored in clear text in whatever cache storage you have configured (typically Memcached or Redis). This has been fixed in 1.12. After upgrading, users should be sure to delete any clear text passwords that have been stored. For example, if you're using the database session backend, you'll likely want to delete any session record from the database and purge that data from any database backups or replicas. In addition, affected organizations who have suffered a database breach while using an affected version should inform their users that their clear text passwords have been compromised. All organizations should encourage users whose passwords were insecurely stored to change these passwords on any sites where they were used. As a workaround, wwitching Django's session storage to use signed cookies instead of the database or cache lessens the impact of this issue, but should not be done without a thorough understanding of the security tradeoffs of using signed cookies rather than a server-side session storage. There is no way to fully mitigate the issue without upgrading. See: CVE-2020-15105. | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-two-factor-auth version less then 1.12 have ### Response: Having vulnarability CVE-2020-15105 Advisory: Django Two-Factor Authentication before 1.12, stores the user's password in clear text in the user session (base64-encoded). The password is stored in the session when the user submits their username and password, and is removed once they complete authentication by entering a two-factor authentication code. This means that the password is stored in clear text in the session for an arbitrary amount of time, and potentially forever if the user begins the login process by entering their username and password and then leaves before entering their two-factor authentication code. The severity of this issue depends on which type of session storage you have configured: in the worst case, if you're using Django's default database session storage, then users' passwords are stored in clear text in your database. In the best case, if you're using Django's signed cookie session, then users' passwords are only stored in clear text within their browser's cookie store. In the common case of using Django's cache session store, the users' passwords are stored in clear text in whatever cache storage you have configured (typically Memcached or Redis). This has been fixed in 1.12. After upgrading, users should be sure to delete any clear text passwords that have been stored. For example, if you're using the database session backend, you'll likely want to delete any session record from the database and purge that data from any database backups or replicas. In addition, affected organizations who have suffered a database breach while using an affected version should inform their users that their clear text passwords have been compromised. All organizations should encourage users whose passwords were insecurely stored to change these passwords on any sites where they were used. As a workaround, wwitching Django's session storage to use signed cookies instead of the database or cache lessens the impact of this issue, but should not be done without a thorough understanding of the security tradeoffs of using signed cookies rather than a server-side session storage. There is no way to fully mitigate the issue without upgrading. See: CVE-2020-15105. | what vulnarability does django-two-factor-auth version less then 1.12 have | |
Having vulnarability PVE-2021-36744 Advisory: Django-ucamlookup 1.9.2 fixes lack of escaping in select2 calls.
https://github.com/uisautomation/django-ucamlookup/commit/5e25e4765637ea4b9e0bf5fcd5e9a922abee7eb3 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-ucamlookup version less then 1.9.2 have ### Response: Having vulnarability PVE-2021-36744 Advisory: Django-ucamlookup 1.9.2 fixes lack of escaping in select2 calls.
https://github.com/uisautomation/django-ucamlookup/commit/5e25e4765637ea4b9e0bf5fcd5e9a922abee7eb3 | what vulnarability does django-ucamlookup version less then 1.9.2 have | |
Having vulnarability PVE-2021-25796 Advisory: Django-uni-form 0.9.0 fixes a XSS security issue. Errors weren't rendered safe: field's input was part of the error message, unsanitized.
https://github.com/pydanny/django-uni-form/pull/98 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-uni-form version less then 0.9.0 have ### Response: Having vulnarability PVE-2021-25796 Advisory: Django-uni-form 0.9.0 fixes a XSS security issue. Errors weren't rendered safe: field's input was part of the error message, unsanitized.
https://github.com/pydanny/django-uni-form/pull/98 | what vulnarability does django-uni-form version less then 0.9.0 have | |
Having vulnarability PVE-2021-42099 Advisory: Django-unicorn version 0.29.0 sanitizes initial JSON to prevent XSS.
https://github.com/adamghill/django-unicorn/commit/c38e2a8bbb3ec6a8cdba30813282d9159c90f0d2 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-unicorn version less then 0.29.0 have ### Response: Having vulnarability PVE-2021-42099 Advisory: Django-unicorn version 0.29.0 sanitizes initial JSON to prevent XSS.
https://github.com/adamghill/django-unicorn/commit/c38e2a8bbb3ec6a8cdba30813282d9159c90f0d2 | what vulnarability does django-unicorn version less then 0.29.0 have | |
Having vulnarability PVE-2022-47794 Advisory: Django-url-security 0.0.2 updates its dependency 'mkdocs' to version '1.3.0' to include a fix for a Cross-Site Scripting vulnerability.
https://github.com/Edrolo/django-url-security/commit/858bab7be8b5dc7e871c1177ef6a2153d5aea5a4 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-url-security version less then 0.0.2 have ### Response: Having vulnarability PVE-2022-47794 Advisory: Django-url-security 0.0.2 updates its dependency 'mkdocs' to version '1.3.0' to include a fix for a Cross-Site Scripting vulnerability.
https://github.com/Edrolo/django-url-security/commit/858bab7be8b5dc7e871c1177ef6a2153d5aea5a4 | what vulnarability does django-url-security version less then 0.0.2 have | |
Having vulnarability CVE-2020-13596 Advisory: Django-urlconf-export 1.1.1 updates Django to v3.0.7 to include security fixes. | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-urlconf-export version less then 1.1.1 have ### Response: Having vulnarability CVE-2020-13596 Advisory: Django-urlconf-export 1.1.1 updates Django to v3.0.7 to include security fixes. | what vulnarability does django-urlconf-export version less then 1.1.1 have | |
Having vulnarability PVE-2021-34774 Advisory: Django-user-accounts before 2.0.2 has a potential security issue with leaking password reset tokens through HTTP Referer header.
https://github.com/pinax/django-user-accounts/issues/258 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-user-accounts version less then 2.0.2 have ### Response: Having vulnarability PVE-2021-34774 Advisory: Django-user-accounts before 2.0.2 has a potential security issue with leaking password reset tokens through HTTP Referer header.
https://github.com/pinax/django-user-accounts/issues/258 | what vulnarability does django-user-accounts version less then 2.0.2 have | |
Having vulnarability CVE-2016-9190 Advisory: Django-user-management 18.0.0 updates its dependency 'pillow' to a version >3.3.2 to include security fixes. | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-user-management version less then 18.0.0 have ### Response: Having vulnarability CVE-2016-9190 Advisory: Django-user-management 18.0.0 updates its dependency 'pillow' to a version >3.3.2 to include security fixes. | what vulnarability does django-user-management version less then 18.0.0 have | |
Having vulnarability CVE-2020-5224 Advisory: In Django User Sessions (django-user-sessions) before 1.7.1, the views provided allow users to terminate specific sessions. The session key is used to identify sessions, and thus included in the rendered HTML. In itself this is not a problem. However if the website has an XSS vulnerability, the session key could be extracted by the attacker and a session takeover could happen. See: CVE-2020-5224. | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-user-sessions version less then 1.7.1 have ### Response: Having vulnarability CVE-2020-5224 Advisory: In Django User Sessions (django-user-sessions) before 1.7.1, the views provided allow users to terminate specific sessions. The session key is used to identify sessions, and thus included in the rendered HTML. In itself this is not a problem. However if the website has an XSS vulnerability, the session key could be extracted by the attacker and a session takeover could happen. See: CVE-2020-5224. | what vulnarability does django-user-sessions version less then 1.7.1 have | |
Having vulnarability PVE-2022-45296 Advisory: Django-userena-ce 4.0.0 uses class based auth views to fix leaking of password reset token.
https://github.com/django-userena-ce/django-userena-ce/commit/210a50fd227a1ccec2c857f5b75712011656c23b | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-userena-ce version less then 4.0.0 have ### Response: Having vulnarability PVE-2022-45296 Advisory: Django-userena-ce 4.0.0 uses class based auth views to fix leaking of password reset token.
https://github.com/django-userena-ce/django-userena-ce/commit/210a50fd227a1ccec2c857f5b75712011656c23b | what vulnarability does django-userena-ce version less then 4.0.0 have | |
Having vulnarability PVE-2021-25797 Advisory: Django-watchman 0.10.0 improves security by keeping tokens out of logs.
https://github.com/mwarkentin/django-watchman/issues/73 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-watchman version less then 0.10.0 have ### Response: Having vulnarability PVE-2021-25797 Advisory: Django-watchman 0.10.0 improves security by keeping tokens out of logs.
https://github.com/mwarkentin/django-watchman/issues/73 | what vulnarability does django-watchman version less then 0.10.0 have | |
Having vulnarability PVE-2023-59135 Advisory: Django-webix 1.2.0 includes a fix for a CSRF vulnerability.
https://github.com/MPASolutions/django-webix/commit/4190a0934e8389d6f73687331d6814ad9fdec358 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-webix version less then 1.2.0 have ### Response: Having vulnarability PVE-2023-59135 Advisory: Django-webix 1.2.0 includes a fix for a CSRF vulnerability.
https://github.com/MPASolutions/django-webix/commit/4190a0934e8389d6f73687331d6814ad9fdec358 | what vulnarability does django-webix version less then 1.2.0 have | |
Having vulnarability CVE-2022-22818 Advisory: Django-websocket 0.3.0 and prior use a version of 'Django' (1.4.1) with known vulnerabilities. | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-websocket version less then equal to 0.3.0 have ### Response: Having vulnarability CVE-2022-22818 Advisory: Django-websocket 0.3.0 and prior use a version of 'Django' (1.4.1) with known vulnerabilities. | what vulnarability does django-websocket version less then equal to 0.3.0 have | |
Having vulnarability CVE-2020-18704 Advisory: Unrestricted Upload of File with Dangerous Type in Django-Widgy v0.8.4 allows remote attackers to execute arbitrary code via the 'image' widget in the component 'Change Widgy Page' (https://github.com/fusionbox/django-widgy/issues/387). See CVE-2020-18704. | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-widgy version equal to 0.8.4 have ### Response: Having vulnarability CVE-2020-18704 Advisory: Unrestricted Upload of File with Dangerous Type in Django-Widgy v0.8.4 allows remote attackers to execute arbitrary code via the 'image' widget in the component 'Change Widgy Page' (https://github.com/fusionbox/django-widgy/issues/387). See CVE-2020-18704. | what vulnarability does django-widgy version equal to 0.8.4 have | |
Having vulnarability CVE-2024-28865 Advisory: django-wiki is a wiki system for Django. Installations of django-wiki prior to version 0.10.1 are vulnerable to maliciously crafted article content that can cause severe use of server CPU through a regular expression loop. Version 0.10.1 fixes this issue. As a workaround, close off access to create and edit articles by anonymous users. See CVE-2024-28865. | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-wiki version less then 0.10.1 have ### Response: Having vulnarability CVE-2024-28865 Advisory: django-wiki is a wiki system for Django. Installations of django-wiki prior to version 0.10.1 are vulnerable to maliciously crafted article content that can cause severe use of server CPU through a regular expression loop. Version 0.10.1 fixes this issue. As a workaround, close off access to create and edit articles by anonymous users. See CVE-2024-28865. | what vulnarability does django-wiki version less then 0.10.1 have | |
Having vulnarability CVE-2021-23727 Advisory: Django-wm 2.0.0 updates the celery dependency to versions =< 5.2.2 due to the CVE-2021-23727.
https://github.com/beatonma/django-wm/compare/1.3.1...2.0.0#diff-fa602a8a75dc9dcc92261bac5f533c2a85e34fcceaff63b3a3a81d9acde2fc52R28 | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-wm version less then 2.0.0 have ### Response: Having vulnarability CVE-2021-23727 Advisory: Django-wm 2.0.0 updates the celery dependency to versions =< 5.2.2 due to the CVE-2021-23727.
https://github.com/beatonma/django-wm/compare/1.3.1...2.0.0#diff-fa602a8a75dc9dcc92261bac5f533c2a85e34fcceaff63b3a3a81d9acde2fc52R28 | what vulnarability does django-wm version less then 2.0.0 have | |
Having vulnarability CVE-2020-25659 Advisory: Django-x509 0.9.1 updates the minimum version of 'cryptography' to 3.2 for security reasons. | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does django-x509 version less then 0.9.1 have ### Response: Having vulnarability CVE-2020-25659 Advisory: Django-x509 0.9.1 updates the minimum version of 'cryptography' to 3.2 for security reasons. | what vulnarability does django-x509 version less then 0.9.1 have | |
Having vulnarability PVE-2021-36834 Advisory: Djangocms-admin-style 1.2.5 fixes a potential security issue if the 'Site.name' field contains malicious code.
https://github.com/django-cms/djangocms-admin-style/pull/375/files | Below is an instruction that describes a task. Write a response that appropriately completes the request. ### Instruction: what vulnarability does djangocms-admin-style version less then 1.2.5 have ### Response: Having vulnarability PVE-2021-36834 Advisory: Djangocms-admin-style 1.2.5 fixes a potential security issue if the 'Site.name' field contains malicious code.
https://github.com/django-cms/djangocms-admin-style/pull/375/files | what vulnarability does djangocms-admin-style version less then 1.2.5 have |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.