python-django - Debian Package Tracker

general

source: python-django (main)
version: 3:4.2.21-1
maintainer: Debian Python Team (DMD)
uploaders: Luke Faraone [DMD] – Chris Lamb [DMD] – Raphaël Hertzog [DMD] – Brian May [DMD]
arch: all
std-ver: 4.7.2
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 1:1.11.29-1~deb10u1
o-o-sec: 1:1.11.29-1+deb10u11
oldstable: 2:2.2.28-1~deb11u2
old-sec: 2:2.2.28-1~deb11u6
old-bpo: 3:3.2.19-1+deb12u1~bpo11+1
stable: 3:3.2.19-1+deb12u1
stable-sec: 3:3.2.19-1+deb12u1
stable-bpo: 3:4.2.21-1~bpo12+1
stable-p-u: 3:3.2.19-1+deb12u2
testing: 3:4.2.21-1
unstable: 3:4.2.21-1
exp: 3:5.2-1

versioned links

1:1.11.29-1~deb10u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1:1.11.29-1+deb10u11: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2:2.2.28-1~deb11u2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2:2.2.28-1~deb11u6: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3:3.2.19-1+deb12u1~bpo11+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3:3.2.19-1+deb12u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3:3.2.19-1+deb12u2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3:4.2.21-1~bpo12+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3:4.2.21-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3:5.2-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

python-django-doc
python3-django (4 bugs: 0, 3, 1, 0)

action needed

The VCS repository is not up to date, push the missing commits. high

vcswatch reports that the current version of the package is not in its VCS.
Either you need to push your commits and/or your tags, or the information about the package's VCS are out of date. A common cause of the latter issue when using the Git VCS is not specifying the correct branch when the packaging is not in the default one (remote HEAD branch), which is usually "master" but can be modified in salsa.debian.org in the project's general settings with the "Default Branch" field). Alternatively the Vcs-Git field in debian/control can contain a "-b <branch-name>" suffix to indicate what branch is used for the Debian packaging.

Created: 2022-08-03 Last update: 2025-05-30 22:30

15 security issues in bullseye high

There are 15 open security issues in bullseye.

1 important issue:

CVE-2025-32873: An issue was discovered in Django 4.2 before 4.2.21, 5.1 before 5.1.9, and 5.2 before 5.2.1. The django.utils.html.strip_tags() function is vulnerable to a potential denial-of-service (slow performance) when processing inputs containing large sequences of incomplete HTML tags. The template filter striptags is also vulnerable, because it is built on top of strip_tags().

14 issues postponed or untriaged:

CVE-2023-41164: (postponed; to be fixed through a stable update) In Django 3.2 before 3.2.21, 4.1 before 4.1.11, and 4.2 before 4.2.5, django.utils.encoding.uri_to_iri() is subject to a potential DoS (denial of service) attack via certain inputs with a very large number of Unicode characters.
CVE-2023-43665: (postponed; to be fixed through a stable update) In Django 3.2 before 3.2.22, 4.1 before 4.1.12, and 4.2 before 4.2.6, the django.utils.text.Truncator chars() and words() methods (when used with html=True) are subject to a potential DoS (denial of service) attack via certain inputs with very long, potentially malformed HTML text. The chars() and words() methods are used to implement the truncatechars_html and truncatewords_html template filters, which are thus also vulnerable. NOTE: this issue exists because of an incomplete fix for CVE-2019-14232.
CVE-2024-24680: (postponed; to be fixed through a stable update) An issue was discovered in Django 3.2 before 3.2.24, 4.2 before 4.2.10, and Django 5.0 before 5.0.2. The intcomma template filter was subject to a potential denial-of-service attack when used with very long strings.
CVE-2024-27351: (postponed; to be fixed through a stable update) In Django 3.2 before 3.2.25, 4.2 before 4.2.11, and 5.0 before 5.0.3, the django.utils.text.Truncator.words() method (with html=True) and the truncatewords_html template filter are subject to a potential regular expression denial-of-service attack via a crafted string. NOTE: this issue exists because of an incomplete fix for CVE-2019-14232 and CVE-2023-43665.
CVE-2024-38875: (postponed; to be fixed through a stable update) An issue was discovered in Django 4.2 before 4.2.14 and 5.0 before 5.0.7. urlize and urlizetrunc were subject to a potential denial of service attack via certain inputs with a very large number of brackets.
CVE-2024-39329: (postponed; to be fixed through a stable update) An issue was discovered in Django 5.0 before 5.0.7 and 4.2 before 4.2.14. The django.contrib.auth.backends.ModelBackend.authenticate() method allows remote attackers to enumerate users via a timing attack involving login requests for users with an unusable password.
CVE-2024-39330: (postponed; to be fixed through a stable update) An issue was discovered in Django 5.0 before 5.0.7 and 4.2 before 4.2.14. Derived classes of the django.core.files.storage.Storage base class, when they override generate_filename() without replicating the file-path validations from the parent class, potentially allow directory traversal via certain inputs during a save() call. (Built-in Storage sub-classes are unaffected.)
CVE-2024-39614: (postponed; to be fixed through a stable update) An issue was discovered in Django 5.0 before 5.0.7 and 4.2 before 4.2.14. get_supported_language_variant() was subject to a potential denial-of-service attack when used with very long strings containing specific characters.
CVE-2024-41989: (postponed; to be fixed through a stable update) An issue was discovered in Django 5.0 before 5.0.8 and 4.2 before 4.2.15. The floatformat template filter is subject to significant memory consumption when given a string representation of a number in scientific notation with a large exponent.
CVE-2024-41990: (postponed; to be fixed through a stable update) An issue was discovered in Django 5.0 before 5.0.8 and 4.2 before 4.2.15. The urlize() and urlizetrunc() template filters are subject to a potential denial-of-service attack via very large inputs with a specific sequence of characters.
CVE-2024-41991: (postponed; to be fixed through a stable update) An issue was discovered in Django 5.0 before 5.0.8 and 4.2 before 4.2.15. The urlize and urlizetrunc template filters, and the AdminURLFieldWidget widget, are subject to a potential denial-of-service attack via certain inputs with a very large number of Unicode characters.
CVE-2024-42005: (postponed; to be fixed through a stable update) An issue was discovered in Django 5.0 before 5.0.8 and 4.2 before 4.2.15. QuerySet.values() and values_list() methods on models with a JSONField are subject to SQL injection in column aliases via a crafted JSON object key as a passed *arg.
CVE-2024-45230: (postponed; to be fixed through a stable update) An issue was discovered in Django 5.1 before 5.1.1, 5.0 before 5.0.9, and 4.2 before 4.2.16. The urlize() and urlizetrunc() template filters are subject to a potential denial-of-service attack via very large inputs with a specific sequence of characters.
CVE-2024-45231: (postponed; to be fixed through a stable update) An issue was discovered in Django v5.1.1, v5.0.9, and v4.2.16. The django.contrib.auth.forms.PasswordResetForm class, when used in a view implementing password reset flows, allows remote attackers to enumerate user e-mail addresses by sending password reset requests and observing the outcome (only when e-mail sending is consistently failing).

Created: 2025-05-07 Last update: 2025-05-24 04:31

13 security issues in bookworm high

There are 13 open security issues in bookworm.

5 important issues:

CVE-2024-53907: An issue was discovered in Django 5.1 before 5.1.4, 5.0 before 5.0.10, and 4.2 before 4.2.17. The strip_tags() method and striptags template filter are subject to a potential denial-of-service attack via certain inputs containing large sequences of nested incomplete HTML entities.
CVE-2024-53908: An issue was discovered in Django 5.1 before 5.1.4, 5.0 before 5.0.10, and 4.2 before 4.2.17. Direct usage of the django.db.models.fields.json.HasKey lookup, when an Oracle database is used, is subject to SQL injection if untrusted data is used as an lhs value. (Applications that use the jsonfield.has_key lookup via __ are unaffected.)
CVE-2024-56374: An issue was discovered in Django 5.1 before 5.1.5, 5.0 before 5.0.11, and 4.2 before 4.2.18. Lack of upper-bound limit enforcement in strings passed when performing IPv6 validation could lead to a potential denial-of-service attack. The undocumented and private functions clean_ipv6_address and is_valid_ipv6_address are vulnerable, as is the django.forms.GenericIPAddressField form field. (The django.db.models.GenericIPAddressField model field is not affected.)
CVE-2025-26699: An issue was discovered in Django 5.1 before 5.1.7, 5.0 before 5.0.13, and 4.2 before 4.2.20. The django.utils.text.wrap() method and wordwrap template filter are subject to a potential denial-of-service attack when used with very long strings.
CVE-2025-32873: An issue was discovered in Django 4.2 before 4.2.21, 5.1 before 5.1.9, and 5.2 before 5.2.1. The django.utils.html.strip_tags() function is vulnerable to a potential denial-of-service (slow performance) when processing inputs containing large sequences of incomplete HTML tags. The template filter striptags is also vulnerable, because it is built on top of strip_tags().

8 issues left for the package maintainer to handle:

CVE-2023-41164: (postponed; to be fixed through a stable update) In Django 3.2 before 3.2.21, 4.1 before 4.1.11, and 4.2 before 4.2.5, django.utils.encoding.uri_to_iri() is subject to a potential DoS (denial of service) attack via certain inputs with a very large number of Unicode characters.
CVE-2023-43665: (postponed; to be fixed through a stable update) In Django 3.2 before 3.2.22, 4.1 before 4.1.12, and 4.2 before 4.2.6, the django.utils.text.Truncator chars() and words() methods (when used with html=True) are subject to a potential DoS (denial of service) attack via certain inputs with very long, potentially malformed HTML text. The chars() and words() methods are used to implement the truncatechars_html and truncatewords_html template filters, which are thus also vulnerable. NOTE: this issue exists because of an incomplete fix for CVE-2019-14232.
CVE-2024-24680: (postponed; to be fixed through a stable update) An issue was discovered in Django 3.2 before 3.2.24, 4.2 before 4.2.10, and Django 5.0 before 5.0.2. The intcomma template filter was subject to a potential denial-of-service attack when used with very long strings.
CVE-2024-27351: (postponed; to be fixed through a stable update) In Django 3.2 before 3.2.25, 4.2 before 4.2.11, and 5.0 before 5.0.3, the django.utils.text.Truncator.words() method (with html=True) and the truncatewords_html template filter are subject to a potential regular expression denial-of-service attack via a crafted string. NOTE: this issue exists because of an incomplete fix for CVE-2019-14232 and CVE-2023-43665.
CVE-2024-38875: (needs triaging) An issue was discovered in Django 4.2 before 4.2.14 and 5.0 before 5.0.7. urlize and urlizetrunc were subject to a potential denial of service attack via certain inputs with a very large number of brackets.
CVE-2024-41990: (needs triaging) An issue was discovered in Django 5.0 before 5.0.8 and 4.2 before 4.2.15. The urlize() and urlizetrunc() template filters are subject to a potential denial-of-service attack via very large inputs with a specific sequence of characters.
CVE-2024-45230: (needs triaging) An issue was discovered in Django 5.1 before 5.1.1, 5.0 before 5.0.9, and 4.2 before 4.2.16. The urlize() and urlizetrunc() template filters are subject to a potential denial-of-service attack via very large inputs with a specific sequence of characters.
CVE-2024-45231: (needs triaging) An issue was discovered in Django v5.1.1, v5.0.9, and v4.2.16. The django.contrib.auth.forms.PasswordResetForm class, when used in a view implementing password reset flows, allows remote attackers to enumerate user e-mail addresses by sending password reset requests and observing the outcome (only when e-mail sending is consistently failing).

You can find information about how to handle these issues in the security team's documentation.

6 issues that should be fixed with the next stable update:

CVE-2024-39329: An issue was discovered in Django 5.0 before 5.0.7 and 4.2 before 4.2.14. The django.contrib.auth.backends.ModelBackend.authenticate() method allows remote attackers to enumerate users via a timing attack involving login requests for users with an unusable password.
CVE-2024-39330: An issue was discovered in Django 5.0 before 5.0.7 and 4.2 before 4.2.14. Derived classes of the django.core.files.storage.Storage base class, when they override generate_filename() without replicating the file-path validations from the parent class, potentially allow directory traversal via certain inputs during a save() call. (Built-in Storage sub-classes are unaffected.)
CVE-2024-39614: An issue was discovered in Django 5.0 before 5.0.7 and 4.2 before 4.2.14. get_supported_language_variant() was subject to a potential denial-of-service attack when used with very long strings containing specific characters.
CVE-2024-41989: An issue was discovered in Django 5.0 before 5.0.8 and 4.2 before 4.2.15. The floatformat template filter is subject to significant memory consumption when given a string representation of a number in scientific notation with a large exponent.
CVE-2024-41991: An issue was discovered in Django 5.0 before 5.0.8 and 4.2 before 4.2.15. The urlize and urlizetrunc template filters, and the AdminURLFieldWidget widget, are subject to a potential denial-of-service attack via certain inputs with a very large number of Unicode characters.
CVE-2024-42005: An issue was discovered in Django 5.0 before 5.0.8 and 4.2 before 4.2.15. QuerySet.values() and values_list() methods on models with a JSONField are subject to SQL injection in column aliases via a crafted JSON object key as a passed *arg.

Created: 2023-09-04 Last update: 2025-05-24 04:31

lintian reports 5 warnings high

Lintian reports 5 warnings about this package. You should make the package lintian clean getting rid of them.

Created: 2024-09-04 Last update: 2024-10-06 03:32

Does not build reproducibly during testing normal

A package building reproducibly enables third parties to verify that the source matches the distributed binaries. It has been identified that this source package produced different results, failed to build or had other issues in a test environment. Please read about how to improve the situation!

Created: 2025-01-08 Last update: 2025-05-30 20:02

Multiarch hinter reports 1 issue(s) low

There are issues with the multiarch metadata for this package.

python-django-doc could be marked Multi-Arch: foreign

Created: 2023-09-25 Last update: 2025-05-30 20:03

debian/patches: 2 patches to forward upstream low

Among the 5 debian patches available in version 3:4.2.21-1 of the package, we noticed the following issues:

2 patches where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.

Created: 2023-02-26 Last update: 2025-05-11 07:02

Issues found with some translations low

Automatic checks made by the Debian l10n team found some issues with the translations contained in this package. You should check the l10n status report for more information.

Issues can be things such as missing translations, problematic translated strings, outdated PO files, unknown languages, etc.

Created: 2020-02-26 Last update: 2023-09-29 09:41

news

[rss feed]

[2025-05-30] Accepted python-django 3:5.2.1-1 (source) into experimental (Chris Lamb)
[2025-05-26] Accepted python-django 3:4.2.21-1~bpo12+1 (source) into stable-backports (Colin Watson)
[2025-05-24] python-django 3:4.2.21-1 MIGRATED to testing (Debian testing watch)
[2025-05-10] Accepted python-django 3:4.2.21-1 (source) into unstable (Chris Lamb)
[2025-04-08] Accepted python-django 3:4.2.20-1~bpo12+1 (source) into stable-backports (Colin Watson)
[2025-04-04] Accepted python-django 3:5.2-1 (source) into experimental (Chris Lamb)
[2025-03-19] Accepted python-django 3:5.2~rc1-1 (source) into experimental (Chris Lamb)
[2025-03-19] Accepted python-django 2:2.2.28-1~deb11u6 (source) into oldstable-security (Chris Lamb)
[2025-03-09] python-django 3:4.2.20-1 MIGRATED to testing (Debian testing watch)
[2025-03-06] Accepted python-django 3:4.2.20-1 (source) into unstable (Chris Lamb)
[2025-03-02] Accepted python-django 3:4.2.19-1~bpo12+1 (source) into stable-backports (Colin Watson)
[2025-02-19] Accepted python-django 3:5.2~beta1-1 (source) into experimental (Chris Lamb)
[2025-02-08] python-django 3:4.2.19-1 MIGRATED to testing (Debian testing watch)
[2025-02-05] Accepted python-django 3:4.2.19-1 (source) into unstable (Chris Lamb)
[2025-02-05] Accepted python-django 3:4.2.18-1~bpo12+1 (source) into stable-backports (Colin Watson)
[2025-01-23] Accepted python-django 2:2.2.28-1~deb11u5 (source) into oldstable-security (Chris Lamb)
[2025-01-18] python-django 3:4.2.18-1 MIGRATED to testing (Debian testing watch)
[2025-01-16] Accepted python-django 3:5.2~alpha1-1 (source) into experimental (Chris Lamb)
[2025-01-15] Accepted python-django 3:5.1.5-1 (source) into experimental (Chris Lamb)
[2025-01-15] Accepted python-django 3:4.2.18-1 (source) into unstable (Chris Lamb)
[2025-01-10] Accepted python-django 2:2.2.28-1~deb11u4 (source) into oldstable-security (Chris Lamb)
[2025-01-06] python-django 3:4.2.17-2 MIGRATED to testing (Debian testing watch)
[2025-01-02] Accepted python-django 3:4.2.17-2 (source) into unstable (Colin Watson)
[2024-12-31] Accepted python-django 2:2.2.28-1~deb11u3 (source) into oldstable-security (Chris Lamb)
[2024-12-04] Accepted python-django 3:4.2.17-1 (source) into unstable (Chris Lamb)
[2024-12-04] Accepted python-django 3:5.1.4-1 (source) into experimental (Chris Lamb)
[2024-11-05] Accepted python-django 3:5.1.3-1 (source) into experimental (Chris Lamb)
[2024-10-08] Accepted python-django 3:5.1.2-1 (source) into experimental (Chris Lamb)
[2024-09-13] python-django 3:4.2.16-1 MIGRATED to testing (Debian testing watch)
[2024-09-06] Accepted python-django 3:4.2.15-1~bpo12+1 (source all) into stable-backports (Debian FTP Masters) (signed by: Chris Lamb)

bugs [bug history graph]

all: 4
RC: 0
I&N: 3
M&W: 1
F&P: 0
patch: 0

links

homepage
lintian (0, 5)
buildd: logs, exp, reproducibility
popcon
browse source code
edit tags
other distros
security tracker
screenshots
l10n (-, 81)
debian patches
debci

ubuntu

[Information about Ubuntu for Debian Developers]

version: 3:4.2.18-1ubuntu1.1
6 bugs (2 patches)
patches for 3:4.2.18-1ubuntu1.1