Django — свободный фреймворк для веб-приложений на языке Python, использующий шаблон проектирования MVC

An issue was discovered in 6.0 before 6.0.5 and 5.2 before 5.2.14. `dj ...

An issue was discovered in 6.0 before 6.0.5 and 5.2 before 5.2.14. Response headers do not vary on cookies if a session is not modified, but `SESSION_SAVE_EVERY_REQUEST` is `True`. A remote attacker can steal a user's session after that user visits a cached public page. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Cantina for reporting this issue.

An issue was discovered in 6.0 before 6.0.5 and 5.2 before 5.2.14. `django.middleware.cache.UpdateCacheMiddleware` erroneously caches requests where the `Vary` header contained an asterisk (`'*'`). This can lead to private data being stored and served. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Ahmad Sadeddin for reporting this issue.

Django has an Improper Handling of Length Parameter Inconsistency

Django Uses Cache Containing Sensitive Information

Django Uses Persistent Cookies Containing Sensitive Information

Уязвимость программной платформы для веб-приложений Django, связанная с возможностью отправки файла cookie-сеанса, позволяющая нарушителю получить несанкционированный доступ к защищаемой информации

Уязвимость программной платформы для веб-приложений Django, связанная с неправильной обработкой несоответствия параметра длины, позволяющая нарушителю вызвать отказ в обслуживании

Уязвимость модуля django.middleware.cache.UpdateCacheMiddleware программной платформы для веб-приложений Django, позволяющая нарушителю получить несанкционированный доступ к защищаемой информации

An issue was discovered in 6.0 before 6.0.5 and 5.2 before 5.2.14. Response headers do not vary on cookies if a session is not modified, but `SESSION_SAVE_EVERY_REQUEST` is `True`. A remote attacker can steal a user's session after that user visits a cached public page. Earlier, unsupported Django series (such as 5.0.x, 4.1.x, and 3.2.x) were not evaluated and may also be affected. Django would like to thank Cantina for reporting this issue.