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 r2555762e7212 (s390x; channels: 1.18-20.04_beta, 1.18-20.04_edge)
 * libjpeg-turbo8: 5631-1
 * libpcre2-8-0: 5627-1

Revision r28d7360223ce (arm64; channels: edge, latest, 1.18-22.04_beta, 1.18-22.04_edge)
 * libpcre2-8-0: 5627-1

Revision r2cfffa798925 (ppc64le; channels: 1.18-20.04_beta, 1.18-20.04_edge)
 * libjpeg-turbo8: 5631-1
 * libpcre2-8-0: 5627-1

Revision r51b384d02acd (amd64; channels: edge, latest, 1.18-22.04_beta, 1.18-22.04_edge)
 * libpcre2-8-0: 5627-1

Revision r6a62909dc8f2 (arm64; channels: 1.18-20.04_beta, 1.18-20.04_edge)
 * libjpeg-turbo8: 5631-1
 * libpcre2-8-0: 5627-1

Revision rab3624a67b2f (ppc64le; channels: edge, latest, 1.18-22.04_beta, 1.18-22.04_edge)
 * libpcre2-8-0: 5627-1

Revision rafa3c9fb0479 (amd64; channels: 1.18-20.04_beta, 1.18-20.04_edge)
 * libjpeg-turbo8: 5631-1
 * libpcre2-8-0: 5627-1

Revision rbc718bd7d4e8 (s390x; channels: edge, latest, 1.18-22.04_beta, 1.18-22.04_edge)
 * libpcre2-8-0: 5627-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-5627-1/
 * https://ubuntu.com/security/notices/USN-5631-1/