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 r068f6d0d71fa (ppc64le; channels: 2.4-20.04_edge, 2.4-20.04_beta)
 * libpcre2-8-0: 5627-1

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

Revision r7f404c4270e4 (arm64; channels: 2.4-20.04_edge, 2.4-20.04_beta)
 * libpcre2-8-0: 5627-1

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

Revision r86b1889a5a7c (amd64; channels: 2.4-20.04_edge, 2.4-20.04_beta)
 * libpcre2-8-0: 5627-1

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

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

Revision rc7b566905a71 (s390x; channels: edge, latest, 2.4-22.04_edge, 2.4-22.04_beta)
 * 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/