Upstream has issued an advisory today (July 4): https://www.djangoproject.com/weblog/2022/jul/04/security-releases/ The issue is fixed upstream in 3.2.14. Mageia 8 is also affected.
Assignee: bugsquad => pythonWhiteboard: (none) => MGA8TOOStatus comment: (none) => Fixed upstream in 3.2.14
Ubuntu has issued an advisory for this today (July 4): https://ubuntu.com/security/notices/USN-5501-1
python-django-3.2.14-1.mga9 uploaded for Cauldron by Stig-Ørjan.
Whiteboard: MGA8TOO => (none)Version: Cauldron => 8CC: (none) => smelror
Upstream has issued an advisory today (August 3): https://www.djangoproject.com/weblog/2022/aug/03/security-releases/ The issue is fixed upstream in 3.2.15. Mageia 8 is also affected.
Version: 8 => CauldronWhiteboard: (none) => MGA8TOOSummary: python-django new security issue CVE-2022-34265 => python-django new security issues CVE-2022-34265 and CVE-2022-36359Status comment: Fixed upstream in 3.2.14 => Fixed upstream in 3.2.15
Cauldron has been updated to version 3.2.15
Advisory ======== Python-django has been updated to fix 2 security issues CVE-2022-34265: An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6. The Trunc() and Extract() database functions are subject to SQL injection if untrusted data is used as a kind/lookup_name value. Applications that constrain the lookup name and kind choice to a known safe list are unaffected. CVE-2022-36359: An issue was discovered in the HTTP FileResponse class in Django 3.2 before 3.2.15 and 4.0 before 4.0.7. An application is vulnerable to a reflected file download (RFD) attack that sets the Content-Disposition header of a FileResponse when the filename is derived from user-supplied input. References ========== https://nvd.nist.gov/vuln/detail/CVE-2022-34265 https://nvd.nist.gov/vuln/detail/CVE-2022-36359 https://www.djangoproject.com/weblog/2022/aug/03/security-releases/ Files ===== Uploaded to core/updates_testing python-django-3.2.15-1.mga8 from python-django-3.2.15-1.mga8.src.rpm
Version: Cauldron => 8Assignee: python => qa-bugsWhiteboard: MGA8TOO => (none)
Thanks. The built package is actually called python3-django.
Status comment: Fixed upstream in 3.2.15 => (none)
Advisory ======== Python-django has been updated to fix 2 security issues CVE-2022-34265: An issue was discovered in Django 3.2 before 3.2.14 and 4.0 before 4.0.6. The Trunc() and Extract() database functions are subject to SQL injection if untrusted data is used as a kind/lookup_name value. Applications that constrain the lookup name and kind choice to a known safe list are unaffected. CVE-2022-36359: An issue was discovered in the HTTP FileResponse class in Django 3.2 before 3.2.15 and 4.0 before 4.0.7. An application is vulnerable to a reflected file download (RFD) attack that sets the Content-Disposition header of a FileResponse when the filename is derived from user-supplied input. References ========== https://nvd.nist.gov/vuln/detail/CVE-2022-34265 https://nvd.nist.gov/vuln/detail/CVE-2022-36359 https://www.djangoproject.com/weblog/2022/jul/04/security-releases/ https://www.djangoproject.com/weblog/2022/aug/03/security-releases/ Files ===== Uploaded to core/updates_testing python3-django-3.2.15-1.mga8 from python-django-3.2.15-1.mga8.src.rpm
(In reply to David Walser from comment #3) > Upstream has issued an advisory today (August 3): > https://www.djangoproject.com/weblog/2022/aug/03/security-releases/ > > The issue is fixed upstream in 3.2.15. > > Mageia 8 is also affected. Ubuntu has issued an advisory for this on August 4: https://ubuntu.com/security/notices/USN-5549-1
Mageia8, x86_64 Followed Herman's lead in this as in bug 29737. Removed the former mysite directory and ran the same commands as before with identical results, so no regressions for python3. $ django-admin startproject mysite $ python manage.py migrate $ python manage.py runserver The server reported success at localhost:8000/ with the cute rocket icon and link to documentation. Moved to another terminal: $ python manage.py startapp polls Noted the same stub scripts in the polls directory. Stopped the server with Control-C.
CC: (none) => tarazed25Whiteboard: (none) => MGA8-64-OK
Validating. Advisory in Comment 7.
Keywords: (none) => validated_updateCC: (none) => andrewsfarm, sysadmin-bugs
Keywords: (none) => advisoryCC: (none) => davidwhodgins
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGASA-2022-0281.html
Status: NEW => RESOLVEDResolution: (none) => FIXED