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 r36b527c86686 (arm64; channels: 1.6-21.10_edge, edge, 1.6-21.10_beta, latest)
* zlib1g: 5355-1
Revision r46962f6a29f1 (amd64; channels: 1.5-20.04_beta, 1.5-20.04_edge)
* zlib1g: 5355-1
Revision r514052a797f2 (s390x; channels: 1.6-21.10_edge, edge, 1.6-21.10_beta, latest)
* zlib1g: 5355-1
Revision r6f9e59ade060 (ppc64le; channels: 1.6-21.10_edge, edge, 1.6-21.10_beta, latest)
* zlib1g: 5355-1
Revision r85805278f426 (amd64; channels: 1.6-21.10_edge, edge, 1.6-21.10_beta, latest)
* zlib1g: 5355-1
Revision rbfbfd7a74426 (s390x; channels: 1.5-20.04_beta, 1.5-20.04_edge)
* zlib1g: 5355-1
Revision rf2341d698e08 (arm64; channels: 1.5-20.04_beta, 1.5-20.04_edge)
* zlib1g: 5355-1
Revision rf29b6a09edc7 (ppc64le; channels: 1.5-20.04_beta, 1.5-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/