mirror of
https://github.com/django/django.git
synced 2025-03-06 07:22:32 +00:00
[5.2.x] Refs #35612 -- Extended docs on how the security team evaluates reports.
Co-authored-by: Shai Berger <shai@platonix.com> Backport of f609a2da868b2320ecdc0551df3cca360d5b5bc3 from main.
This commit is contained in:
parent
209d0f6143
commit
d6a44efa49
@ -49,8 +49,14 @@ requires a security release:
|
||||
* The vulnerability is within a :ref:`supported version <security-support>` of
|
||||
Django.
|
||||
|
||||
* The vulnerability applies to a production-grade Django application. This means
|
||||
the following do not require a security release:
|
||||
* The vulnerability does not depend on manual actions that rely on code
|
||||
external to Django. This includes actions performed by a project's developer
|
||||
or maintainer using developer tools or the Django CLI. For example, attacks
|
||||
that require running management commands with uncommon or insecure options
|
||||
do not qualify.
|
||||
|
||||
* The vulnerability applies to a production-grade Django application. This
|
||||
means the following scenarios do not require a security release:
|
||||
|
||||
* Exploits that only affect local development, for example when using
|
||||
:djadmin:`runserver`.
|
||||
|
Loading…
x
Reference in New Issue
Block a user