diff options
| author | Natalia <124304+nessita@users.noreply.github.com> | 2024-02-06 12:14:12 -0300 |
|---|---|---|
| committer | Natalia <124304+nessita@users.noreply.github.com> | 2024-02-06 12:17:11 -0300 |
| commit | b9170b4a9e7f0dde5d29ef69354c94efa6d6edfb (patch) | |
| tree | 44dcc81711b622a6dc9864125dafa0b7b07d1e22 | |
| parent | e5350a931a017fab6aa0026e8f2d6e9ef09e1e1b (diff) | |
[3.2.x] Added CVE-2024-24680 to security archive.
Backport of c650c1412d1933e339cc93f9b6745c3eedb1c25b from main
| -rw-r--r-- | docs/releases/security.txt | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/docs/releases/security.txt b/docs/releases/security.txt index cf63dafa0d..7df74adb82 100644 --- a/docs/releases/security.txt +++ b/docs/releases/security.txt @@ -36,6 +36,17 @@ Issues under Django's security process All security issues have been handled under versions of Django's security process. These are listed below. +February 6, 2024 - :cve:`2024-24680` +------------------------------------ + +Potential denial-of-service in ``intcomma`` template filter. +`Full description +<https://www.djangoproject.com/weblog/2024/feb/06/security-releases/>`__ + +* Django 5.0 :commit:`(patch) <16a8fe18a3b81250f4fa57e3f93f0599dc4895bc>` +* Django 4.2 :commit:`(patch) <572ea07e84b38ea8de0551f4b4eda685d91d09d2>` +* Django 3.2 :commit:`(patch) <c1171ffbd570db90ca206c30f8e2b9f691243820>` + November 1, 2023 - :cve:`2023-46695` ------------------------------------ |