ubuntu-docker-images team mailing list archive

[Athos Ribeiro <athos.ribeiro@xxxxxxxxxxxxx>]

On Fri, Jul 29, 2022 at 05:14:20AM +0000, security-team-toolbox-bot@xxxxxxxxxxxxx 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 r236ad022bccc (ppc64le; channels: 2.4-22.04_edge, latest, 2.4-22.04_beta, edge)
> * libtirpc-common: 5538-1
> * libtirpc3: 5538-1
>
> Revision r5fbada5c0d01 (arm64; channels: 2.4-22.04_edge, latest, 2.4-22.04_beta, edge)
> * libtirpc-common: 5538-1
> * libtirpc3: 5538-1
>
> Revision r74f4881bb239 (amd64; channels: 2.4-22.04_edge, latest, 2.4-22.04_beta, edge)
> * libtirpc-common: 5538-1
> * libtirpc3: 5538-1
>
> Revision rc5fa64a591ca (s390x; channels: 2.4-22.04_edge, latest, 2.4-22.04_beta, edge)
> * libtirpc-common: 5538-1
> * libtirpc3: 5538-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-5538-1/

These images were re-built and re-tagged.

--
Athos Ribeiro