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 r22d2a839a474 (s390x; channels: 1.5-20.04_edge, 1.5-20.04_beta)
 * libgnutls30: 5550-1

Revision r2771a297c2d8 (ppc64le; channels: 1.5-20.04_edge, 1.5-20.04_beta)
 * libgnutls30: 5550-1

Revision r4786a6f2d733 (s390x; channels: latest, 1.6-22.04_beta, edge, 1.6-22.04_edge)
 * libgnutls30: 5550-1

Revision r536a527a8d76 (amd64; channels: 1.5-20.04_edge, 1.5-20.04_beta)
 * libgnutls30: 5550-1

Revision r8e7578ef2261 (ppc64le; channels: latest, 1.6-22.04_beta, edge, 1.6-22.04_edge)
 * libgnutls30: 5550-1

Revision rb23757a75e09 (arm64; channels: latest, 1.6-22.04_beta, edge, 1.6-22.04_edge)
 * libgnutls30: 5550-1

Revision rc44d85619209 (amd64; channels: latest, 1.6-22.04_beta, edge, 1.6-22.04_edge)
 * libgnutls30: 5550-1

Revision red36ec67afd0 (arm64; channels: 1.5-20.04_edge, 1.5-20.04_beta)
 * libgnutls30: 5550-1

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-5550-1/