Skip to content

Commit 1f2a565

Browse files
committed
Adjusted default DoS severity level in Security Policy.
1 parent 71d1e92 commit 1f2a565

1 file changed

Lines changed: 10 additions & 3 deletions

File tree

docs/internals/security.txt

Lines changed: 10 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -347,8 +347,10 @@ will not issue patches or new releases for those versions.
347347
Security issue severity levels
348348
==============================
349349

350-
The severity level of a security vulnerability is determined by the attack
351-
type.
350+
The severity level of a security vulnerability is determined primarily by the
351+
attack type. The Django Security Team retains the authority to adjust severity
352+
levels based on the specific characteristics, context, and potential real-world
353+
impact of individual vulnerabilities.
352354

353355
Severity levels are:
354356

@@ -361,16 +363,21 @@ Severity levels are:
361363

362364
* Cross site scripting (XSS)
363365
* Cross site request forgery (CSRF)
364-
* Denial-of-service attacks
365366
* Broken authentication
366367

367368
* **Low**
368369

370+
* Denial-of-service attacks
369371
* Sensitive data exposure
370372
* Broken session management
371373
* Unvalidated redirects/forwards
372374
* Issues requiring an uncommon configuration option
373375

376+
For example, a denial-of-service vulnerability that is exploitable by
377+
unauthenticated attackers and affects default Django configurations, causing
378+
severe performance degradation or service unavailability, may be elevated to
379+
**Moderate**, given the potential impact across the Django ecosystem.
380+
374381
.. _security-disclosure:
375382

376383
How Django discloses security issues

0 commit comments

Comments
 (0)