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 r18a1e6887c75 (s390x; channels: 1.6-23.04_edge, 1.6-23.04_beta, edge, latest)
 * libc-bin: 6409-1
 * libc6: 6409-1

Revision r29b5691a603a (s390x; channels: 1.6-22.04_edge, 1.6-22.04_beta)
 * libc-bin: 6409-1
 * libc6: 6409-1

Revision r2d6cf1069df7 (arm64; channels: 1.6-23.04_edge, 1.6-23.04_beta, edge, latest)
 * libc-bin: 6409-1
 * libc6: 6409-1

Revision r6486088f4618 (ppc64le; channels: 1.6-22.04_edge, 1.6-22.04_beta)
 * libc-bin: 6409-1
 * libc6: 6409-1

Revision r8b0f17e0b335 (amd64; channels: 1.6-22.04_edge, 1.6-22.04_beta)
 * libc-bin: 6409-1
 * libc6: 6409-1

Revision r8b89273d385a (ppc64le; channels: 1.6-23.04_edge, 1.6-23.04_beta, edge, latest)
 * libc-bin: 6409-1
 * libc6: 6409-1

Revision rafd951688cd0 (arm64; channels: 1.6-22.04_edge, 1.6-22.04_beta)
 * libc-bin: 6409-1
 * libc6: 6409-1

Revision rb01a66265205 (amd64; channels: 1.6-23.04_edge, 1.6-23.04_beta, edge, latest)
 * libc-bin: 6409-1
 * libc6: 6409-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-6409-1/