update to 19.03.11

Bug #1881679 reported by Michael Hudson-Doyle
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
docker.io (Ubuntu)
Fix Released
Undecided
Unassigned
Bionic
Fix Released
Undecided
Unassigned
Eoan
Won't Fix
Undecided
Unassigned
Focal
Fix Released
Undecided
Unassigned

Bug Description

[impact]
It fixes CVE-2020-13401

[test case]
per https://wiki.ubuntu.com/DockerUpdates, our test case is the autopkgtests

[regression potential]
As usual, we deliver most benefit to our users by delivering an upstream experience. A risk of regressions is part of that.

CVE References

Changed in docker.io (Ubuntu):
status: New → In Progress
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package docker.io - 19.03.11-0ubuntu1

---------------
docker.io (19.03.11-0ubuntu1) groovy; urgency=medium

  * Update to 19.03.11 upstream release (CVE-2020-13401, LP: #1881679)
  * Apply wrap-and-sort
  * Move cgroupfs-mount to Suggests
    (esp. on Ubuntu where systemd is canonical)

 -- Tianon Gravi <email address hidden> Mon, 01 Jun 2020 15:14:15 -0700

Changed in docker.io (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote :

The Eoan Ermine has reached end of life, so this bug will not be fixed for that release

Changed in docker.io (Ubuntu Eoan):
status: New → Won't Fix
Revision history for this message
Sharebear (jonny-sharebear) wrote :

Over 6 months without getting this update into any of the LTS releases. Security scanning tools such as those used on Azure are flagging this vulnerability on VMs. Is there any timeline for when this update is coming or should I switch to the docker repositories?

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package docker.io - 20.10.2-0ubuntu1~20.04.2

---------------
docker.io (20.10.2-0ubuntu1~20.04.2) focal; urgency=medium

  * d/rules: pass --no-restart-after-upgrade to dh_installsystemd.
    The --no-start flag we pass to dh_installsystemd in d/rules is supposed
    to also disable --restart-after-upgrade, however, this feature was buggy
    before the now fixed debhelper 13. Due to that we need to manually add
    --no-restart-after-upgrade.

docker.io (20.10.2-0ubuntu1~20.04.1) focal; urgency=medium

  * Backport version 20.10.2-0ubuntu1 from Hirsute (LP: #1919322).

 -- Lucas Kanashiro <email address hidden> Mon, 29 Mar 2021 16:10:09 -0300

Changed in docker.io (Ubuntu Focal):
status: New → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package docker.io - 20.10.2-0ubuntu1~18.04.2

---------------
docker.io (20.10.2-0ubuntu1~18.04.2) bionic; urgency=medium

  * d/rules: pass --no-restart-after-upgrade to dh_installsystemd.
    The --no-start flag we pass to dh_installsystemd in d/rules is supposed
    to also disable --restart-after-upgrade, however, this feature was buggy
    before the now fixed debhelper 13. Due to that we need to manually add
    --no-restart-after-upgrade.

docker.io (20.10.2-0ubuntu1~18.04.1) bionic; urgency=medium

  * Backport version 20.10.2-0ubuntu1 from Hirsute (LP: #1919322).
    - d/control: do not b-d on libbtrfs-dev, it is not available in Bionic.

 -- Lucas Kanashiro <email address hidden> Mon, 29 Mar 2021 16:27:41 -0300

Changed in docker.io (Ubuntu Bionic):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.