ubuntu-docker-images team mailing list archive

[Paulo Machado <paulo.machado@xxxxxxxxxxxxx>]

 These images were re-built and re-tagged.

On Fri, Jul 29, 2022 at 2:14 AM <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 r8134b0c79b93 (arm64; channels: 14-22.04_edge, 14-22.04_beta,
> latest, edge)
>  * libtirpc-common: 5538-1
>  * libtirpc3: 5538-1
>
> Revision r83e16cbabfdd (ppc64le; channels: 14-22.04_edge, 14-22.04_beta,
> latest, edge)
>  * libtirpc-common: 5538-1
>  * libtirpc3: 5538-1
>
> Revision rb30da7b08f4a (amd64; channels: 14-22.04_edge, 14-22.04_beta,
> latest, edge)
>  * libtirpc-common: 5538-1
>  * libtirpc3: 5538-1
>
> Revision rf84cdb96607d (s390x; channels: 14-22.04_edge, 14-22.04_beta,
> latest, 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/
>