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 r2115e98948a6 (ppc64le; channels: 2.4-22.04_beta, 2.4-22.04_edge)
 * libc-bin: 6409-1
 * libc6: 6409-1

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

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

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

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

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

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

Revision rdfeeec91b8b4 (arm64; channels: 2.4-22.04_beta, 2.4-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/