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 r50b2440db145 (arm64; channels: 1.5-20.04_beta, 1.5-20.04_edge)
 * libpcre2-8-0: 5627-1

Revision r52c27d02fc72 (s390x; channels: edge, latest, 1.6-22.04_beta, 1.6-22.04_edge)
 * libpcre2-8-0: 5627-1

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

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

Revision r7abfa19bffca (s390x; channels: 1.5-20.04_beta, 1.5-20.04_edge)
 * libpcre2-8-0: 5627-1

Revision ra121464d507f (ppc64le; channels: 1.5-20.04_beta, 1.5-20.04_edge)
 * libpcre2-8-0: 5627-1

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

Revision rfa34df0b87ba (amd64; channels: 1.5-20.04_beta, 1.5-20.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/