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 r19b18155438b (s390x; channels: 2.4-20.04_beta, 2.4-20.04_edge)
 * libexpat1: 5638-3

Revision r508c2644e44f (amd64; channels: 2.4-20.04_beta, 2.4-20.04_edge)
 * libexpat1: 5638-3

Revision r5162c526f933 (ppc64le; channels: 2.4-22.04_edge, 2.4-22.04_beta)
 * libexpat1: 5638-3

Revision r56f107a6e3de (s390x; channels: 2.4-22.04_edge, 2.4-22.04_beta)
 * libexpat1: 5638-3

Revision r8165e6d40bb6 (ppc64le; channels: 2.4-20.04_beta, 2.4-20.04_edge)
 * libexpat1: 5638-3

Revision ra3e7b3673d1f (amd64; channels: 2.4-22.04_edge, 2.4-22.04_beta)
 * libexpat1: 5638-3

Revision rbd3bb58f1046 (arm64; channels: 2.4-22.04_edge, 2.4-22.04_beta)
 * libexpat1: 5638-3

Revision rd797c4bb5784 (arm64; channels: 2.4-20.04_beta, 2.4-20.04_edge)
 * libexpat1: 5638-3

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-5638-3/