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 r17259d54e689 (arm64; channels: edge, latest, 8.0-22.04_edge, 8.0-22.04_beta)
 * libpcre2-8-0: 5627-1

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

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

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

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

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

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

Revision reba1708c2443 (s390x; channels: 8.0-20.04_edge, 8.0-20.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/