mirror of
https://github.com/django/django.git
synced 2025-06-05 03:29:12 +00:00
Refs #35612 -- Extended docs on how the security team evaluates reports.
Co-authored-by: Shai Berger <shai@platonix.com>
This commit is contained in:
parent
1330cb5705
commit
f609a2da86
@ -49,8 +49,14 @@ requires a security release:
|
|||||||
* The vulnerability is within a :ref:`supported version <security-support>` of
|
* The vulnerability is within a :ref:`supported version <security-support>` of
|
||||||
Django.
|
Django.
|
||||||
|
|
||||||
* The vulnerability applies to a production-grade Django application. This means
|
* The vulnerability does not depend on manual actions that rely on code
|
||||||
the following do not require a security release:
|
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
|
* Exploits that only affect local development, for example when using
|
||||||
:djadmin:`runserver`.
|
:djadmin:`runserver`.
|
||||||
|
Loading…
x
Reference in New Issue
Block a user