From aa5293068782dfa2d2173c75c8477f58a9989942 Mon Sep 17 00:00:00 2001 From: Natalia <124304+nessita@users.noreply.github.com> Date: Tue, 3 Sep 2024 11:19:02 -0300 Subject: [PATCH] Added CVE-2024-45230 and CVE-2024-45231 to security archive. --- docs/releases/security.txt | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/docs/releases/security.txt b/docs/releases/security.txt index f7e8cedee6..b83be59dbb 100644 --- a/docs/releases/security.txt +++ b/docs/releases/security.txt @@ -36,6 +36,28 @@ Issues under Django's security process All security issues have been handled under versions of Django's security process. These are listed below. +September 3, 2024 - :cve:`2024-45231` +------------------------------------- + +Potential user email enumeration via response status on password reset. +`Full description +`__ + +* Django 5.1 :commit:`(patch) <3c733c78d6f8e50296d6e248968b6516c92a53ca>` +* Django 5.0 :commit:`(patch) <96d84047715ea1715b4bd1594e46122b8a77b9e2>` +* Django 4.2 :commit:`(patch) ` + +September 3, 2024 - :cve:`2024-45230` +------------------------------------- + +Potential denial-of-service vulnerability in ``django.utils.html.urlize()``. +`Full description +`__ + +* Django 5.1 :commit:`(patch) <022ab0a75c76ab2ea31dfcc5f2cf5501e378d397>` +* Django 5.0 :commit:`(patch) <813de2672bd7361e9a453ab62cd6e52f96b6525b>` +* Django 4.2 :commit:`(patch) ` + August 6, 2024 - :cve:`2024-42005` ----------------------------------