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 r05051599ba2e (amd64; channels: 9.18-22.04_beta, 9.18-22.04_edge)
 * libc-bin: 6409-1
 * libc6: 6409-1

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

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

Revision r6702d6611bad (s390x; channels: 9.18-23.04_beta, edge, latest, 9.18-23.04_edge)
 * libc-bin: 6409-1
 * libc6: 6409-1

Revision r860d79712c73 (amd64; channels: 9.18-23.04_beta, edge, latest, 9.18-23.04_edge)
 * libc-bin: 6409-1
 * libc6: 6409-1

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

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

Revision rf06875a26353 (s390x; channels: 9.18-22.04_beta, 9.18-22.04_edge)
 * 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/