Results of 1 - 10 of about 46 for intended (0.002 sec.)
- Django 3.1.13 リリースノート — Django 6.1 ドキュメント 15073
- Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 3.1.13 リリースノート ¶ July 1, 2021 Django 3.1.13 fixes a security issue with severity "high" in 3.1.12. CVE-2021-35042: Potential SQL injec
... tion via unsanitized QuerySet.order_by() input ¶ Unsanitized user input passed to QuerySet.order_by() could bypass intended column reference validation in path marked for deprecation resulting in a potential SQL injection even if a deprecation wa ... ence validation path リリースノート July fixes security severity high Potential unsanitized Unsanitized user passed bypass intended marked resulting クイック検索 Last update: 2026年10月09日 « previous | up | next » ...
-
https://man.mtool.work/django/6.1/releases/3.1.13.html
- Django 3.1.13 リリースノート — Django 6.1 ドキュメント 9840
- Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 3.1.13 リリースノート ¶ July 1, 2021 Django 3.1.13 fixes a security issue with severity "high" in 3.1.12. CVE-2021-35042: Potential SQL injec
... tion via unsanitized QuerySet.order_by() input ¶ Unsanitized user input passed to QuerySet.order_by() could bypass intended column reference validation in path marked for deprecation resulting in a potential SQL injection even if a deprecation wa ...
-
https://man.mtool.work/django/6.1/releases/3.1.13.html
- Django 3.2.5 リリースノート — Django 6.1 ドキュメント 9428
- Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 3.2.5 リリースノート ¶ July 1, 2021 Django 3.2.5 では、 3.2.4 における深刻度 "high" のセキュリティの問題1件と、いくつかのバグを修正しました。
... QL injection via unsanitized QuerySet.order_by() input ¶ Unsanitized user input passed to QuerySet.order_by() could bypass intended column reference validation in path marked for deprecation resulting in a potential SQL injection even if a deprecation wa ...
-
https://man.mtool.work/django/6.1/releases/3.2.5.html
- Django 3.2.5 リリースノート — Django 6.1 ドキュメント 9031
- Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 3.2.5 リリースノート ¶ July 1, 2021 Django 3.2.5 では、 3.2.4 における深刻度 "high" のセキュリティの問題1件と、いくつかのバグを修正しました。
... QL injection via unsanitized QuerySet.order_by() input ¶ Unsanitized user input passed to QuerySet.order_by() could bypass intended column reference validation in path marked for deprecation resulting in a potential SQL injection even if a deprecation wa ...
-
https://man.mtool.work/django/6.1/releases/3.2.5.html
- Django 1.3.5 リリースノート — Django 6.1 ドキュメント 9031
- Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.3.5 リリースノート ¶ December 10, 2012 Django 1.3.5 addresses two security issues present in previous Django releases in the 1.3 series. Pl
... and a hostname, and checks that the URL is either relative, or if absolute matches the supplied hostname. This function is intended for use whenever user-supplied redirect targets are accepted, to ensure that such redirects cannot lead to arbitrary third ...
-
https://man.mtool.work/django/6.1/releases/1.3.5.html
- Django 1.4.3 リリースノート — Django 6.1 ドキュメント 9031
- Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.4.3 リリースノート ¶ December 10, 2012 Django 1.4.3 addresses two security issues present in previous Django releases in the 1.4 series. Pl
... and a hostname, and checks that the URL is either relative, or if absolute matches the supplied hostname. This function is intended for use whenever user-supplied redirect targets are accepted, to ensure that such redirects cannot lead to arbitrary third ...
-
https://man.mtool.work/django/6.1/releases/1.4.3.html
- Django 1.3.5 リリースノート — Django 6.1 ドキュメント 8634
- Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.3.5 リリースノート ¶ December 10, 2012 Django 1.3.5 addresses two security issues present in previous Django releases in the 1.3 series. Pl
... and a hostname, and checks that the URL is either relative, or if absolute matches the supplied hostname. This function is intended for use whenever user-supplied redirect targets are accepted, to ensure that such redirects cannot lead to arbitrary third ...
-
https://man.mtool.work/django/6.1/releases/1.3.5.html
- Django 1.3.6 リリースノート — Django 6.1 ドキュメント 8634
- Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.3.6 リリースノート ¶ February 19, 2013 Django 1.3.6 fixes four security issues present in previous Django releases in the 1.3 series. This
... tity expansion. Django uses this parser for deserializing XML-formatted database fixtures. The fixture deserializer is not intended for use with untrusted data, but in order to err on the side of safety in Django 1.3.6 the XML deserializer refuses to par ...
-
https://man.mtool.work/django/6.1/releases/1.3.6.html
- Django 1.4.3 リリースノート — Django 6.1 ドキュメント 8634
- Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.4.3 リリースノート ¶ December 10, 2012 Django 1.4.3 addresses two security issues present in previous Django releases in the 1.4 series. Pl
... and a hostname, and checks that the URL is either relative, or if absolute matches the supplied hostname. This function is intended for use whenever user-supplied redirect targets are accepted, to ensure that such redirects cannot lead to arbitrary third ...
-
https://man.mtool.work/django/6.1/releases/1.4.3.html
- Django 1.3.6 リリースノート — Django 6.1 ドキュメント 8634
- Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.3.6 リリースノート ¶ February 19, 2013 Django 1.3.6 fixes four security issues present in previous Django releases in the 1.3 series. This
... tity expansion. Django uses this parser for deserializing XML-formatted database fixtures. The fixture deserializer is not intended for use with untrusted data, but in order to err on the side of safety in Django 1.3.6 the XML deserializer refuses to par ...
-
https://man.mtool.work/django/6.1/releases/1.3.6.html