ubuntu-docker-images team mailing list archive

[Athos Ribeiro <athos.ribeiro@xxxxxxxxxxxxx>]

On Tue, Feb 27, 2024 at 05:00:43AM +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 r1f03f93b21ea (amd64; channels: 2.4-20.04_beta, 2.4-20.04_edge)
> * libxml2: 6658-1
>
> Revision r420fc89630ed (ppc64le; channels: 2.4-20.04_beta, 2.4-20.04_edge)
> * libxml2: 6658-1
>
> Revision r60db635324c6 (ppc64le; channels: 2.4-22.04_beta, 2.4-22.04_edge)
> * libxml2: 6658-1
>
> Revision r67a80889cbfc (amd64; channels: 2.4-22.04_beta, 2.4-22.04_edge)
> * libxml2: 6658-1
>
> Revision r92481d21aa22 (s390x; channels: 2.4-20.04_beta, 2.4-20.04_edge)
> * libxml2: 6658-1
>
> Revision rdc195174908d (arm64; channels: 2.4-20.04_beta, 2.4-20.04_edge)
> * libxml2: 6658-1
>
> Revision re46ad319e5ed (s390x; channels: 2.4-22.04_beta, 2.4-22.04_edge)
> * libxml2: 6658-1
>
> Revision rf19d435e768f (arm64; channels: 2.4-22.04_beta, 2.4-22.04_edge)
> * libxml2: 6658-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-6658-1/

These images have been re-built and re-tagged.

--
Athos Ribeiro