diff options
| author | Carlton Gibson <carlton.gibson@noumenal.es> | 2021-06-02 11:15:54 +0200 |
|---|---|---|
| committer | Carlton Gibson <carlton.gibson@noumenal.es> | 2021-06-02 11:16:43 +0200 |
| commit | 1aa7bcf48276891499ce9bfb46d926d191e83e0b (patch) | |
| tree | a5b00e306a465a44b29c1c4fe3ad4fd790468424 | |
| parent | d128f46ceb0c6deb6e9924dfc4cb91da4e654381 (diff) | |
[3.2.x] Added CVE-2021-33203 and CVE-2021-33571 to security archive.
Backport of a39f235ca4cb7370dba3a3dedeaab0106d27792f from main
| -rw-r--r-- | docs/releases/security.txt | 27 |
1 files changed, 27 insertions, 0 deletions
diff --git a/docs/releases/security.txt b/docs/releases/security.txt index d6f979663a..ace57648ae 100644 --- a/docs/releases/security.txt +++ b/docs/releases/security.txt @@ -36,6 +36,33 @@ Issues under Django's security process All security issues have been handled under versions of Django's security process. These are listed below. +June 2, 2021 - :cve:`2021-33203` +------------------------------- + +Potential directory traversal via ``admindocs``. `Full description +<https://www.djangoproject.com/weblog/2021/jun/02/security-releases/>`__ + +Versions affected +~~~~~~~~~~~~~~~~~ + +* Django 3.2 :commit:`(patch) <dfaba12cda060b8b292ae1d271b44bf810b1c5b9>` +* Django 3.1 :commit:`(patch) <20c67a0693c4ede2b09af02574823485e82e4c8f>` +* Django 2.2 :commit:`(patch) <053cc9534d174dc89daba36724ed2dcb36755b90>` + +June 2, 2021 - :cve:`2021-33571` +------------------------------- + +Possible indeterminate SSRF, RFI, and LFI attacks since validators accepted +leading zeros in IPv4 addresses. `Full description +<https://www.djangoproject.com/weblog/2021/jun/02/security-releases/>`__ + +Versions affected +~~~~~~~~~~~~~~~~~ + +* Django 3.2 :commit:`(patch) <9f75e2e562fa0c0482f3dde6fc7399a9070b4a3d>` +* Django 3.1 :commit:`(patch) <203d4ab9ebcd72fc4d6eb7398e66ed9e474e118e>` +* Django 2.2 :commit:`(patch) <f27c38ab5d90f68c9dd60cabef248a570c0be8fc>` + May 6, 2021 - :cve:`2021-32052` ------------------------------- |