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 r42a09c80be23 (amd64; channels: 1.18-20.04_edge, 1.18-20.04_beta)
 * perl-base: 5689-1

Revision r50d323bc90fb (ppc64le; channels: 1.18-20.04_edge, 1.18-20.04_beta)
 * perl-base: 5689-1

Revision r5dc976148975 (ppc64le; channels: 1.18-22.04_beta, 1.18-22.04_edge)
 * perl-base: 5689-1

Revision r88b87f8f178c (s390x; channels: 1.18-20.04_edge, 1.18-20.04_beta)
 * perl-base: 5689-1

Revision rb4af6a4d0df0 (amd64; channels: 1.18-22.04_beta, 1.18-22.04_edge)
 * perl-base: 5689-1

Revision rbdaf87f153c0 (s390x; channels: 1.18-22.04_beta, 1.18-22.04_edge)
 * perl-base: 5689-1

Revision rcfdec1ddee1d (arm64; channels: 1.18-22.04_beta, 1.18-22.04_edge)
 * perl-base: 5689-1

Revision rd57c691753c7 (arm64; channels: 1.18-20.04_edge, 1.18-20.04_beta)
 * perl-base: 5689-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-5689-1/