ubuntu-docker-images team mailing list archive

[security-team-toolbox-bot@xxxxxxxxxxxxx]

A scan of this rock shows that it was built with packages from the Ubuntu
archive that have since received security updates. The following lists new
USNs for affected binary packages in each rock revision:

Revision r220ee010bf29 (ppc64le; channels: 1.18-20.04_edge, 1.18-20.04_beta)
 * zlib1g: 5570-2

Revision r31d75ba3ec80 (amd64; channels: 1.18-20.04_edge, 1.18-20.04_beta)
 * zlib1g: 5570-2

Revision r34e6702f5a10 (amd64; channels: 1.18-22.04_edge, latest, edge, 1.18-22.04_beta)
 * zlib1g: 5570-2

Revision r47f1951732fe (ppc64le; channels: 1.18-22.04_edge, latest, edge, 1.18-22.04_beta)
 * zlib1g: 5570-2

Revision rae7298e7e13e (s390x; channels: 1.18-20.04_edge, 1.18-20.04_beta)
 * zlib1g: 5570-2

Revision rbba7590e7de5 (arm64; channels: 1.18-22.04_edge, latest, edge, 1.18-22.04_beta)
 * zlib1g: 5570-2

Revision rc3ec0e6579fc (arm64; channels: 1.18-20.04_edge, 1.18-20.04_beta)
 * zlib1g: 5570-2

Revision rfc32b301d5d8 (s390x; channels: 1.18-22.04_edge, latest, edge, 1.18-22.04_beta)
 * zlib1g: 5570-2

Simply rebuilding the rock will pull in the new security updates and
resolve this. If your rock also contains vendored code, now might be a
good time to review it for any needed updates.

Thank you for your rock and for attending to this matter.

References:
 * https://ubuntu.com/security/notices/USN-5570-2/