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 r0a71040919d2 (arm64; channels: 2.4-20.04_edge, 2.4-20.04_beta)
 * zlib1g: 5570-2

Revision r203bf0e3fa94 (s390x; channels: 2.4-20.04_edge, 2.4-20.04_beta)
 * zlib1g: 5570-2

Revision r3986d4eba56e (amd64; channels: 2.4-22.04_beta, latest, 2.4-22.04_edge, edge)
 * zlib1g: 5570-2

Revision rb55f915af895 (ppc64le; channels: 2.4-22.04_beta, latest, 2.4-22.04_edge, edge)
 * zlib1g: 5570-2

Revision rc7b738aa61a9 (ppc64le; channels: 2.4-20.04_edge, 2.4-20.04_beta)
 * zlib1g: 5570-2

Revision rca54a60ec268 (s390x; channels: 2.4-22.04_beta, latest, 2.4-22.04_edge, edge)
 * zlib1g: 5570-2

Revision re90cfc4f6793 (arm64; channels: 2.4-22.04_beta, latest, 2.4-22.04_edge, edge)
 * zlib1g: 5570-2

Revision rf1ff40a83def (amd64; channels: 2.4-20.04_edge, 2.4-20.04_beta)
 * zlib1g: 5570-2

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-5570-2/