python-django - Debian Package Tracker

general

source: python-django (main)
version: 2:3.2.7-4
maintainer: Debian Python Team (DMD)
uploaders: Brian May [DMD] – Raphaël Hertzog [DMD] – Chris Lamb [DMD] – Luke Faraone [DMD]
arch: all
std-ver: 4.6.0.1
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.10.7-2+deb9u9
o-o-sec: 1:1.10.7-2+deb9u14
o-o-bpo: 1:1.11.20-1~bpo9+1
oldstable: 1:1.11.29-1~deb10u1
old-sec: 1:1.11.29-1~deb10u1
old-bpo: 2:2.2.24-1~bpo10+1
stable: 2:2.2.24-1
testing: 2:2.2.24-1
unstable: 2:3.2.7-4
exp: 2:4.0~alpha1-1

versioned links

1:1.10.7-2+deb9u9: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1:1.10.7-2+deb9u14: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1:1.11.20-1~bpo9+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1:1.11.29-1~deb10u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2:2.2.24-1~bpo10+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2:2.2.24-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2:3.2.7-4: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2:4.0~alpha1-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

python-django-doc
python3-django (2 bugs: 1, 1, 0, 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: 2021-09-22 Last update: 2021-09-22 16:06

4 security issues in buster high

There are 4 open security issues in buster.

3 important issues:

CVE-2021-31542: In Django 2.2 before 2.2.21, 3.1 before 3.1.9, and 3.2 before 3.2.1, MultiPartParser, UploadedFile, and FieldFile allowed directory traversal via uploaded files with suitably crafted file names.
CVE-2021-33203: Django before 2.2.24, 3.x before 3.1.12, and 3.2.x before 3.2.4 has a potential directory traversal via django.contrib.admindocs. Staff members could use the TemplateDetailView view to check the existence of arbitrary files. Additionally, if (and only if) the default admindocs templates have been customized by application developers to also show file contents, then not only the existence but also the file contents would have been exposed. In other words, there is directory traversal outside of the template root directories.
CVE-2021-33571: In Django 2.2 before 2.2.24, 3.x before 3.1.12, and 3.2 before 3.2.4, URLValidator, validate_ipv4_address, and validate_ipv46_address do not prohibit leading zero characters in octal literals. This may allow a bypass of access control that is based on IP addresses. (validate_ipv4_address and validate_ipv46_address are unaffected with Python 3.9.5+..) .

1 issue left for the package maintainer to handle:

CVE-2021-28658: (needs triaging) In Django 2.2 before 2.2.20, 3.0 before 3.0.14, and 3.1 before 3.1.8, MultiPartParser allowed directory traversal via uploaded files with suitably crafted file names. Built-in upload handlers were not affected by this vulnerability.

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

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

CVE-2020-24583: An issue was discovered in Django 2.2 before 2.2.16, 3.0 before 3.0.10, and 3.1 before 3.1.1 (when Python 3.7+ is used). FILE_UPLOAD_DIRECTORY_PERMISSIONS mode was not applied to intermediate-level directories created in the process of uploading files. It was also not applied to intermediate-level collected static directories when using the collectstatic management command.
CVE-2020-24584: An issue was discovered in Django 2.2 before 2.2.16, 3.0 before 3.0.10, and 3.1 before 3.1.1 (when Python 3.7+ is used). The intermediate-level directories of the filesystem cache had the system's standard umask rather than 0o077.
CVE-2021-23336: The package python/cpython from 0 and before 3.6.13, from 3.7.0 and before 3.7.10, from 3.8.0 and before 3.8.8, from 3.9.0 and before 3.9.2 are vulnerable to Web Cache Poisoning via urllib.parse.parse_qsl and urllib.parse.parse_qs by using a vector called parameter cloaking. When the attacker can separate query parameters using a semicolon (;), they can cause a difference in the interpretation of the request between the proxy (running with default configuration) and the server. This can result in malicious requests being cached as completely safe ones, as the proxy would usually not see the semicolon as a separator, and therefore would not include it in a cache key of an unkeyed parameter.
CVE-2021-3281: In Django 2.2 before 2.2.18, 3.0 before 3.0.12, and 3.1 before 3.1.6, the django.utils.archive.extract method (used by "startapp --template" and "startproject --template") allows directory traversal via an archive with absolute paths or relative paths with dot segments.

Created: 2021-04-06 Last update: 2021-09-13 18:30

The package has not entered testing even though the delay is over normal

The package has not entered testing even though the 5-day delay is over. Check why.

Created: 2021-09-18 Last update: 2021-09-25 08:35

Fails to build during reproducibility 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: 2021-06-09 Last update: 2021-09-25 06:53

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: 2021-09-11 02:32

testing migrations

excuses:
- Migration status for python-django (2:2.2.24-1 to 2:3.2.7-4): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- Updating python-django introduces new bugs: #983618
- autopkgtest for django-ldapdb/1.5.1-2: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻)
- autopkgtest for django-maintenancemode/0.11.3-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻)
- autopkgtest for django-restricted-resource/2016.8-3: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻)
- autopkgtest for django-setuptest/0.2.1-4: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻)
- autopkgtest for djangorestframework/3.12.1-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻)
- autopkgtest for lava/2020.12-5: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻)
- autopkgtest for python-django/2:3.2.7-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass
- autopkgtest for python-django-analytical/3.0.0-2: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻)
- autopkgtest for python-django-import-export/2.5.0-2: amd64: No test results, arm64: No test results, armhf: No test results, i386: No test results, ppc64el: No test results
- Additional info:
- Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-django.html
- 12 days old (needed 5 days)
- Not considered

news

[rss feed]

[2021-09-22] Accepted python-django 2:4.0~alpha1-1 (source) into experimental (Chris Lamb)
[2021-09-13] Accepted python-django 2:3.2.7-4 (source) into unstable (Chris Lamb)
[2021-09-09] Accepted python-django 2:3.2.7-3 (source) into unstable (Chris Lamb)
[2021-09-09] Accepted python-django 2:3.2.7-2 (source) into experimental (Chris Lamb)
[2021-09-01] Accepted python-django 2:3.2.7-1 (source) into experimental (Chris Lamb)
[2021-08-02] Accepted python-django 2:3.2.6-1 (source) into experimental (Chris Lamb)
[2021-07-15] Accepted python-django 2:3.2.5-2 (source) into experimental (Chris Lamb)
[2021-07-01] Accepted python-django 2:3.2.5-1 (source) into experimental (Chris Lamb)
[2021-06-18] Accepted python-django 2:2.2.24-1~bpo10+1 (source all) into buster-backports->backports-policy, buster-backports (Debian FTP Masters) (signed by: Chris Lamb)
[2021-06-08] python-django 2:2.2.24-1 MIGRATED to testing (Debian testing watch)
[2021-06-05] Accepted python-django 1:1.10.7-2+deb9u14 (source all) into oldstable (Chris Lamb)
[2021-06-02] Accepted python-django 2:2.2.24-1 (source) into unstable (Chris Lamb)
[2021-06-02] Accepted python-django 2:3.2.4-1 (source) into experimental (Chris Lamb)
[2021-05-13] Accepted python-django 2:3.2.3-1 (source) into experimental (Chris Lamb)
[2021-05-13] Accepted python-django 2:2.2.23-1 (source) into unstable (Chris Lamb)
[2021-05-12] python-django 2:2.2.22-1 MIGRATED to testing (Debian testing watch)
[2021-05-06] Accepted python-django 2:3.2.2-1 (source) into experimental (Chris Lamb)
[2021-05-06] Accepted python-django 2:2.2.22-1 (source) into unstable (Chris Lamb)
[2021-05-06] Accepted python-django 1:1.10.7-2+deb9u13 (source all) into oldstable (Chris Lamb)
[2021-05-04] Accepted python-django 2:2.2.21-1 (source) into unstable (Chris Lamb)
[2021-05-04] Accepted python-django 2:3.2.1-1 (source) into experimental (Chris Lamb)
[2021-04-20] Accepted python-django 2:2.2.19-1~bpo10+2 (source all) into buster-backports->backports-policy, buster-backports (Debian FTP Masters) (signed by: Chris Lamb)
[2021-04-16] Accepted python-django 2:2.2.20-1~bpo10+1 (source all) into buster-backports->backports-policy, buster-backports (Debian FTP Masters) (signed by: Chris Lamb)
[2021-04-11] python-django 2:2.2.20-1 MIGRATED to testing (Debian testing watch)
[2021-04-09] Accepted python-django 1:1.10.7-2+deb9u12 (source all) into oldstable (Chris Lamb)
[2021-04-06] Accepted python-django 2:2.2.20-1 (source) into unstable (Chris Lamb)
[2021-04-06] Accepted python-django 2:3.2-1 (source) into experimental (Chris Lamb)
[2021-03-19] Accepted python-django 2:3.2~rc1-1 (source) into experimental (Chris Lamb)
[2021-02-22] Accepted python-django 2:2.2.19-1~bpo10+1 (source all) into buster-backports (Chris Lamb)
[2021-02-22] python-django 2:2.2.19-1 MIGRATED to testing (Debian testing watch)

bugs [bug history graph]

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

links

homepage
buildd: logs, exp, clang, reproducibility
popcon
browse source code
edit tags
other distros
security tracker
screenshots
l10n (-, 79)
debci

ubuntu

[Information about Ubuntu for Debian Developers]

version: 2:2.2.24-1
6 bugs (2 patches)