Debian Package Tracker

general

source: bash (main)
version: 5.0-5
maintainer: Matthias Klose (DMD)
arch: all any
std-ver: 4.4.1
VCS: Bazaar (Browse, QA)

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

[pool directory]

o-o-stable: 4.3-11+deb8u1
o-o-sec: 4.3-11+deb8u2
oldstable: 4.4-5
stable: 5.0-4
testing: 5.0-5
unstable: 5.0-5

versioned links

4.3-11+deb8u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
4.3-11+deb8u2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
4.4-5: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
5.0-4: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
5.0-5: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

bash (401 bugs: 1, 279, 121, 0)
bash-builtins (3 bugs: 0, 1, 2, 0)
bash-doc (2 bugs: 0, 0, 2, 0)
bash-static (1 bugs: 0, 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: 2017-12-03 Last update: 2020-01-21 15:44

1 security issue in bullseye high

There is 1 open security issue in bullseye.

1 important issue:

CVE-2019-18276: An issue was discovered in disable_priv_mode in shell.c in GNU Bash through 5.0 patch 11. By default, if Bash is run with its effective UID not equal to its real UID, it will drop privileges by setting its effective UID to its real UID. However, it does so incorrectly. On Linux and other systems that support "saved UID" functionality, the saved UID is not dropped. An attacker with command execution in the shell can use "enable -f" for runtime loading of a new builtin, which can be a shared object that calls setuid() and therefore regains privileges. However, binaries running with an effective UID of 0 are unaffected.

Please fix it.

Created: 2019-11-28 Last update: 2019-12-04 07:34

1 security issue in sid high

There is 1 open security issue in sid.

1 important issue:

CVE-2019-18276: An issue was discovered in disable_priv_mode in shell.c in GNU Bash through 5.0 patch 11. By default, if Bash is run with its effective UID not equal to its real UID, it will drop privileges by setting its effective UID to its real UID. However, it does so incorrectly. On Linux and other systems that support "saved UID" functionality, the saved UID is not dropped. An attacker with command execution in the shell can use "enable -f" for runtime loading of a new builtin, which can be a shared object that calls setuid() and therefore regains privileges. However, binaries running with an effective UID of 0 are unaffected.

Please fix it.

Created: 2019-11-28 Last update: 2019-12-04 07:34

Depends on packages which need a new maintainer normal

The packages that bash depends on which need a new maintainer are:

texi2html (#698081)
- Build-Depends: texi2html

Created: 2019-11-22 Last update: 2020-01-22 02:07

23 bugs tagged patch in the BTS normal

The BTS contains patches fixing 23 bugs (24 if counting merged bugs), consider including or untagging them.

Created: 2019-04-01 Last update: 2020-01-22 02:00

Multiarch hinter reports 1 issue(s) low

There are issues with the multiarch metadata for this package.

bash-doc could be marked Multi-Arch: foreign

Created: 2016-09-14 Last update: 2020-01-21 21:34

1 ignored security issue in buster low

There is 1 open security issue in buster.

1 issue skipped by the security teams:

CVE-2019-18276: An issue was discovered in disable_priv_mode in shell.c in GNU Bash through 5.0 patch 11. By default, if Bash is run with its effective UID not equal to its real UID, it will drop privileges by setting its effective UID to its real UID. However, it does so incorrectly. On Linux and other systems that support "saved UID" functionality, the saved UID is not dropped. An attacker with command execution in the shell can use "enable -f" for runtime loading of a new builtin, which can be a shared object that calls setuid() and therefore regains privileges. However, binaries running with an effective UID of 0 are unaffected.

Please fix it.

Created: 2019-11-28 Last update: 2019-12-04 07:34

1 ignored security issue in jessie low

There is 1 open security issue in jessie.

1 issue skipped by the security teams:

CVE-2019-18276: An issue was discovered in disable_priv_mode in shell.c in GNU Bash through 5.0 patch 11. By default, if Bash is run with its effective UID not equal to its real UID, it will drop privileges by setting its effective UID to its real UID. However, it does so incorrectly. On Linux and other systems that support "saved UID" functionality, the saved UID is not dropped. An attacker with command execution in the shell can use "enable -f" for runtime loading of a new builtin, which can be a shared object that calls setuid() and therefore regains privileges. However, binaries running with an effective UID of 0 are unaffected.

Please fix it.

Created: 2019-11-28 Last update: 2019-12-04 07:34

1 ignored security issue in stretch low

There is 1 open security issue in stretch.

1 issue skipped by the security teams:

CVE-2019-18276: An issue was discovered in disable_priv_mode in shell.c in GNU Bash through 5.0 patch 11. By default, if Bash is run with its effective UID not equal to its real UID, it will drop privileges by setting its effective UID to its real UID. However, it does so incorrectly. On Linux and other systems that support "saved UID" functionality, the saved UID is not dropped. An attacker with command execution in the shell can use "enable -f" for runtime loading of a new builtin, which can be a shared object that calls setuid() and therefore regains privileges. However, binaries running with an effective UID of 0 are unaffected.

Please fix it.

Created: 2019-11-28 Last update: 2019-12-04 07:34

Build log checks report 2 warnings low

Build log checks report 2 warnings

Created: 2018-05-13 Last update: 2019-01-14 21:14

Standards version of the package is outdated. wishlist

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

Created: 2020-01-21 Last update: 2020-01-21 05:06

news

[rss feed]

[2019-11-15] bash 5.0-5 MIGRATED to testing (Debian testing watch)
[2019-11-10] Accepted bash 5.0-5 (source) into unstable (Matthias Klose)
[2019-04-23] bash 5.0-4 MIGRATED to testing (Debian testing watch)
[2019-04-18] Accepted bash 5.0-4 (source) into unstable (Matthias Klose)
[2019-04-16] bash 5.0-3 MIGRATED to testing (Debian testing watch)
[2019-04-04] Accepted bash 5.0-3 (source) into unstable (Matthias Klose)
[2019-03-25] Accepted bash 4.3-11+deb8u2 (source all amd64) into oldstable (Emilio Pozuelo Monfort)
[2019-01-29] bash 5.0-2 MIGRATED to testing (Debian testing watch)
[2019-01-24] Accepted bash 5.0-2 (source) into unstable (Matthias Klose)
[2019-01-20] bash 5.0-1 MIGRATED to testing (Debian testing watch)
[2019-01-14] Accepted bash 5.0-1 (source) into unstable (Matthias Klose)
[2018-12-06] Accepted bash 5.0~beta2-1 (source) into experimental (Matthias Klose)
[2018-10-22] Accepted bash 5.0~beta1-1 (source) into experimental (Matthias Klose)
[2018-07-09] bash 4.4.18-3.1 MIGRATED to testing (Debian testing watch)
[2018-07-02] Accepted bash 4.4.18-3.1 (source) into unstable (Helmut Grohne)
[2018-06-07] bash 4.4.18-3 MIGRATED to testing (Debian testing watch)
[2018-06-01] Accepted bash 5.0~alpha1-1 (source) into experimental (Matthias Klose)
[2018-06-01] Accepted bash 4.4.18-3 (source) into unstable (Matthias Klose)
[2018-04-11] bash 4.4.18-2 MIGRATED to testing (Debian testing watch)
[2018-04-10] bash 4.4.18-2 MIGRATED to testing (Debian testing watch)
[2018-04-04] Accepted bash 4.4.18-2 (source) into unstable (Matthias Klose)
[2018-02-15] bash 4.4.18-1.1 MIGRATED to testing (Debian testing watch)
[2018-02-13] Accepted bash 4.4.18-1.1 (source) into unstable (Raphaël Hertzog)
[2018-02-11] bash 4.4.18-1 MIGRATED to testing (Debian testing watch)
[2018-02-11] bash 4.4.18-1 MIGRATED to testing (Debian testing watch)
[2018-02-06] Accepted bash 4.4.18-1 (source) into unstable (Matthias Klose)
[2017-05-22] bash 4.4-5 MIGRATED to testing (Debian testing watch)
[2017-05-15] Accepted bash 4.4-5 (source) into unstable (Matthias Klose)
[2017-02-04] bash 4.4-4 MIGRATED to testing (Debian testing watch)
[2017-01-24] Accepted bash 4.4-4 (source) into unstable (Matthias Klose)

bugs [bug history graph]

all: 386 412
RC: 1
I&N: 264 283
M&W: 121 128
F&P: 0
patch: 23 24

links

homepage
buildd: logs, checks, clang, reproducibility, cross
popcon
browse source code
edit tags
security tracker
screenshots

ubuntu

[Information about Ubuntu for Debian Developers]

version: 5.0-5ubuntu1
193 bugs (8 patches)
patches for 5.0-5ubuntu1