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 r1033d9ae74f6 (ppc64le; channels: 1.18-22.04_beta, 1.18-22.04_edge)
 * libexpat1: 5638-2

Revision r4d44b31026ed (s390x; channels: 1.18-22.04_beta, 1.18-22.04_edge)
 * libexpat1: 5638-2

Revision r6e29c0f0d3be (amd64; channels: 1.18-20.04_edge, 1.18-20.04_beta)
 * libexpat1: 5638-2

Revision r807811ff648b (arm64; channels: 1.18-20.04_edge, 1.18-20.04_beta)
 * libexpat1: 5638-2

Revision ra4da5b36943b (arm64; channels: 1.18-22.04_beta, 1.18-22.04_edge)
 * libexpat1: 5638-2

Revision radf1daf2e4fb (s390x; channels: 1.18-20.04_edge, 1.18-20.04_beta)
 * libexpat1: 5638-2

Revision rb81248822808 (amd64; channels: 1.18-22.04_beta, 1.18-22.04_edge)
 * libexpat1: 5638-2

Revision rf69d51746ad1 (ppc64le; channels: 1.18-20.04_edge, 1.18-20.04_beta)
 * libexpat1: 5638-2

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-2/