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 r207a584a6778 (arm64; channels: 13-21.10_beta, edge, 13-21.10_edge, latest)
* zlib1g: 5355-1
Revision r397818294788 (amd64; channels: 12-20.04_edge, 12-20.04_beta)
* zlib1g: 5355-1
Revision r7eab1e505b8e (s390x; channels: 13-21.10_beta, edge, 13-21.10_edge, latest)
* zlib1g: 5355-1
Revision r99d1696cb3a6 (amd64; channels: 13-21.10_beta, edge, 13-21.10_edge, latest)
* zlib1g: 5355-1
Revision ra63a3f758347 (s390x; channels: 12-20.04_edge, 12-20.04_beta)
* zlib1g: 5355-1
Revision rbb222a7234a9 (arm64; channels: 12-20.04_edge, 12-20.04_beta)
* zlib1g: 5355-1
Revision rdff07c86d283 (ppc64le; channels: 12-20.04_edge, 12-20.04_beta)
* zlib1g: 5355-1
Revision re3f92d11732f (ppc64le; channels: 13-21.10_beta, edge, 13-21.10_edge, latest)
* 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/