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 r0df8def2da49 (s390x; channels: 2.4-20.04_beta, 2.4-20.04_edge)
* zlib1g: 5355-1
Revision r23abe86ad6b2 (amd64; channels: edge, 2.4-21.10_edge, 2.4-21.10_beta, latest)
* zlib1g: 5355-1
Revision r29f26b4d15b2 (s390x; channels: edge, 2.4-21.10_edge, 2.4-21.10_beta, latest)
* zlib1g: 5355-1
Revision r3aad1d3e3eef (amd64; channels: 2.4-20.04_beta, 2.4-20.04_edge)
* zlib1g: 5355-1
Revision r70b3500109c6 (ppc64le; channels: 2.4-20.04_beta, 2.4-20.04_edge)
* zlib1g: 5355-1
Revision r8d5fb9ee89a6 (ppc64le; channels: edge, 2.4-21.10_edge, 2.4-21.10_beta, latest)
* zlib1g: 5355-1
Revision r96797a38921f (arm64; channels: edge, 2.4-21.10_edge, 2.4-21.10_beta, latest)
* zlib1g: 5355-1
Revision re873997d9765 (arm64; channels: 2.4-20.04_beta, 2.4-20.04_edge)
* zlib1g: 5355-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-5355-1/
