Images were rebuilt and re-tagged! On Fri, Sep 23, 2022 at 2:13 AM <security-team-toolbox-...@canonical.com> wrote:
> 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 r014567c30221 (ppc64le; channels: edge, latest, 6.0-22.04_beta, > 6.0-22.04_edge) > * libpcre2-8-0: 5627-1 > > Revision r1f5a2a77c275 (s390x; channels: 5.0-20.04_beta, 5.0-20.04_edge) > * libpcre2-8-0: 5627-1 > > Revision r4c272013854e (s390x; channels: edge, latest, 6.0-22.04_beta, > 6.0-22.04_edge) > * libpcre2-8-0: 5627-1 > > Revision r4d3cb58364f4 (ppc64le; channels: 5.0-20.04_beta, 5.0-20.04_edge) > * libpcre2-8-0: 5627-1 > > Revision r88e4f73689bc (amd64; channels: edge, latest, 6.0-22.04_beta, > 6.0-22.04_edge) > * libpcre2-8-0: 5627-1 > > Revision r937669dc0bcd (arm64; channels: 5.0-20.04_beta, 5.0-20.04_edge) > * libpcre2-8-0: 5627-1 > > Revision rb74f769d48f9 (arm64; channels: edge, latest, 6.0-22.04_beta, > 6.0-22.04_edge) > * libpcre2-8-0: 5627-1 > > Revision re6e5676a0530 (amd64; channels: 5.0-20.04_beta, 5.0-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/ >
-- Mailing list: https://launchpad.net/~ubuntu-docker-images Post to : ubuntu-docker-images@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-docker-images More help : https://help.launchpad.net/ListHelp
