Debian Package Tracker

general

source: python2.7 (main)
version: 2.7.15~rc1-1
maintainer: Matthias Klose [DMD]
arch: all any
std-ver: 4.1.3
VCS: Bazaar (Browse, QA)

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

[pool directory]

o-o-stable: 2.7.3-6+deb7u2
o-o-sec: 2.7.3-6+deb7u4
oldstable: 2.7.9-2+deb8u1
stable: 2.7.13-2+deb9u2
testing: 2.7.15~rc1-1
unstable: 2.7.15~rc1-1

versioned links

2.7.3-6+deb7u2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.7.3-6+deb7u4: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.7.9-2+deb8u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.7.13-2+deb9u2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.7.15~rc1-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

idle-python2.7
libpython2.7
libpython2.7-dbg
libpython2.7-dev
libpython2.7-minimal
libpython2.7-stdlib
libpython2.7-testsuite
python2.7
python2.7-dbg
python2.7-dev
python2.7-doc
python2.7-examples
python2.7-minimal

action needed

The VCS repository is not up to date, consider pushing 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, 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: 2017-12-03 Last update: 2018-04-15 02:43

lintian reports 3 errors and 16 warnings high

Lintian reports 3 errors and 16 warnings about this package. You should make the package lintian clean getting rid of them.

Created: 2018-04-11 Last update: 2018-04-11 06:17

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: 2017-02-02 Last update: 2018-04-23 14:13

1 bug tagged help in the BTS normal

The BTS contains 1 bug tagged help, please consider helping the maintainer in dealing with it.

Created: 2017-08-29 Last update: 2018-04-23 13:44

4 ignored security issues in jessie low

There are 4 open security issues in jessie.

4 issues skipped by the security teams:

CVE-2018-1060:
CVE-2018-1061:
CVE-2017-1000158: CPython (aka Python) up to 2.7.13 is vulnerable to an integer overflow in the PyString_DecodeEscape function in stringobject.c, resulting in heap-based buffer overflow (and possible arbitrary code execution)
CVE-2018-1000030: Python 2.7.14 is vulnerable to a Heap-Buffer-Overflow as well as a Heap-Use-After-Free. Python versions prior to 2.7.14 may also be vulnerable and it appears that Python 2.7.17 and prior may also be vulnerable however this has not been confirmed. The vulnerability lies when multiply threads are handling large amounts of data. In both cases there is essentially a race condition that occurs. For the Heap-Buffer-Overflow, Thread 2 is creating the size for a buffer, but Thread1 is already writing to the buffer without knowing how much to write. So when a large amount of data is being processed, it is very easy to cause memory corruption using a Heap-Buffer-Overflow. As for the Use-After-Free, Thread3->Malloc->Thread1->Free's->Thread2-Re-uses-Free'd Memory. The PSRT has stated that this is not a security vulnerability due to the fact that the attacker must be able to run code, however in some situations, such as function as a service, this vulnerability can potentially be used by an attacker to violate a trust boundary, as such the DWF feels this issue deserves a CVE.

Please fix them.

Created: 2017-11-17 Last update: 2018-04-21 20:05

3 ignored security issues in stretch low

There are 3 open security issues in stretch.

3 issues skipped by the security teams:

CVE-2018-1060:
CVE-2018-1061:
CVE-2018-1000030: Python 2.7.14 is vulnerable to a Heap-Buffer-Overflow as well as a Heap-Use-After-Free. Python versions prior to 2.7.14 may also be vulnerable and it appears that Python 2.7.17 and prior may also be vulnerable however this has not been confirmed. The vulnerability lies when multiply threads are handling large amounts of data. In both cases there is essentially a race condition that occurs. For the Heap-Buffer-Overflow, Thread 2 is creating the size for a buffer, but Thread1 is already writing to the buffer without knowing how much to write. So when a large amount of data is being processed, it is very easy to cause memory corruption using a Heap-Buffer-Overflow. As for the Use-After-Free, Thread3->Malloc->Thread1->Free's->Thread2-Re-uses-Free'd Memory. The PSRT has stated that this is not a security vulnerability due to the fact that the attacker must be able to run code, however in some situations, such as function as a service, this vulnerability can potentially be used by an attacker to violate a trust boundary, as such the DWF feels this issue deserves a CVE.

Please fix them.

Created: 2018-02-03 Last update: 2018-04-21 20:05

10 ignored security issues in wheezy low

There are 10 open security issues in wheezy.

10 issues skipped by the security teams:

CVE-2018-1060:
CVE-2018-1061:
CVE-2014-4616: Array index error in the scanstring function in the _json module in Python 2.7 through 3.5 and simplejson before 2.6.1 allows context-dependent attackers to read arbitrary process memory via a negative index value in the idx argument to the raw_decode function.
CVE-2014-4650:
CVE-2013-1753:
CVE-2014-7185: Integer overflow in bufferobject.c in Python before 2.7.8 allows context-dependent attackers to obtain sensitive information from process memory via a large size and offset in a "buffer" function.
CVE-2018-1000030: Python 2.7.14 is vulnerable to a Heap-Buffer-Overflow as well as a Heap-Use-After-Free. Python versions prior to 2.7.14 may also be vulnerable and it appears that Python 2.7.17 and prior may also be vulnerable however this has not been confirmed. The vulnerability lies when multiply threads are handling large amounts of data. In both cases there is essentially a race condition that occurs. For the Heap-Buffer-Overflow, Thread 2 is creating the size for a buffer, but Thread1 is already writing to the buffer without knowing how much to write. So when a large amount of data is being processed, it is very easy to cause memory corruption using a Heap-Buffer-Overflow. As for the Use-After-Free, Thread3->Malloc->Thread1->Free's->Thread2-Re-uses-Free'd Memory. The PSRT has stated that this is not a security vulnerability due to the fact that the attacker must be able to run code, however in some situations, such as function as a service, this vulnerability can potentially be used by an attacker to violate a trust boundary, as such the DWF feels this issue deserves a CVE.
CVE-2013-7440: The ssl.match_hostname function in CPython (aka Python) before 2.7.9 and 3.x before 3.3.3 does not properly handle wildcards in hostnames, which might allow man-in-the-middle attackers to spoof servers via a crafted certificate.
CVE-2014-9365: The HTTP clients in the (1) httplib, (2) urllib, (3) urllib2, and (4) xmlrpclib libraries in CPython (aka Python) 2.x before 2.7.9 and 3.x before 3.4.3, when accessing an HTTPS URL, do not (a) check the certificate against a trust store or verify that the server hostname matches a domain name in the subject's (b) Common Name or (c) subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate.
CVE-2013-1752:

Please fix them.

Created: 2015-07-12 Last update: 2018-04-21 20:05

Build log checks report 1 warning low

Build log checks report 1 warning

Created: 2017-12-05 Last update: 2017-12-05 19:48

Standards version of the package is outdated. wishlist

The package should be updated to follow the last version of Debian Policy (Standards-Version 4.1.4 instead of 4.1.3).

Created: 2018-04-16 Last update: 2018-04-16 20:51

testing migrations

This package will soon be part of the auto-libffi transition. You might want to ensure that your package is ready for it. You can probably find supplementary information in the debian-release archives or in the corresponding release.debian.org bug.

news

[rss feed]

[2018-04-21] python2.7 2.7.15~rc1-1 MIGRATED to testing (Debian testing watch)
[2018-04-15] Accepted python2.7 2.7.15~rc1-1 (source) into unstable (Matthias Klose)
[2018-04-07] python2.7 2.7.14-8 MIGRATED to testing (Debian testing watch)
[2018-04-02] Accepted python2.7 2.7.14-8 (source) into unstable (Matthias Klose)
[2018-03-19] python2.7 2.7.14-7 MIGRATED to testing (Debian testing watch)
[2018-03-13] Accepted python2.7 2.7.14-7 (source) into unstable (Matthias Klose)
[2018-02-12] python2.7 2.7.14-6 MIGRATED to testing (Debian testing watch)
[2018-02-06] Accepted python2.7 2.7.14-6 (source) into unstable (Matthias Klose)
[2018-02-05] Accepted python2.7 2.7.14-5 (source) into unstable (Matthias Klose)
[2017-12-11] python2.7 2.7.14-4 MIGRATED to testing (Debian testing watch)
[2017-12-05] Accepted python2.7 2.7.14-4 (source) into unstable (Matthias Klose)
[2017-12-05] Accepted python2.7 2.7.14-3 (source) into unstable (Matthias Klose)
[2017-11-29] Accepted python2.7 2.7.13-2+deb9u2 (source all amd64) into proposed-updates->stable-new, proposed-updates (Moritz Mühlenhoff)
[2017-11-24] Accepted python2.7 2.7.3-6+deb7u4 (source all amd64) into oldoldstable (Roberto C. Sanchez)
[2017-11-19] Accepted python2.7 2.7.13-2+deb9u1 (source all amd64) into proposed-updates->stable-new, proposed-updates (Kurt Roeckx)
[2017-10-28] python2.7 2.7.14-2 MIGRATED to testing (Debian testing watch)
[2017-10-27] python2.7 2.7.14-2 MIGRATED to testing (Debian testing watch)
[2017-09-17] Accepted python2.7 2.7.14-2 (source) into unstable (Matthias Klose)
[2017-09-17] Accepted python2.7 2.7.14-1 (source) into unstable (Matthias Klose)
[2017-09-05] Accepted python2.7 2.7.14~rc1-3 (source) into unstable (Matthias Klose)
[2017-08-31] Accepted python2.7 2.7.14~rc1-2 (source) into unstable (Matthias Klose)
[2017-08-30] Accepted python2.7 2.7.14~rc1-1 (source) into unstable (Matthias Klose)
[2017-07-23] Accepted python2.7 2.7.13-4 (source) into unstable (Matthias Klose)
[2017-06-08] Accepted python2.7 2.7.13-3 (source) into unstable (Matthias Klose)
[2017-01-30] python2.7 2.7.13-2 MIGRATED to testing (Debian testing watch)
[2017-01-19] Accepted python2.7 2.7.13-2 (source) into unstable (Matthias Klose)
[2016-12-29] python2.7 2.7.13-1 MIGRATED to testing (Debian testing watch)
[2016-12-29] python2.7 2.7.13-1 MIGRATED to testing (Debian testing watch)
[2016-12-18] Accepted python2.7 2.7.13-1 (source) into unstable (Matthias Klose)
[2016-12-15] python2.7 2.7.13~rc1-1 MIGRATED to testing (Debian testing watch)

bugs [bug history graph]

all: 41
RC: 0
I&N: 30
M&W: 11
F&P: 0
help: 1

links

lintian (3, 16)
buildd: logs, checks, clang, reproducibility
popcon
debci
browse source code
edit tags
security tracker
screenshots

ubuntu

[Information about Ubuntu for Debian Developers]

version: 2.7.15~rc1-1
28 bugs (1 patch)