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 r185cf08f8eec (ppc64le; channels: 1.18-20.04_beta, 1.18-20.04_edge)
* zlib1g: 5355-1
Revision r4504bdb5c0a0 (amd64; channels: 1.18-21.10_beta, edge, 1.18-21.10_edge, latest)
* zlib1g: 5355-1
Revision r57a416140d72 (arm64; channels: 1.18-21.10_beta, edge, 1.18-21.10_edge, latest)
* zlib1g: 5355-1
Revision r614e4ec86629 (arm64; channels: 1.18-20.04_beta, 1.18-20.04_edge)
* zlib1g: 5355-1
Revision r6f87dec45cbe (amd64; channels: 1.18-20.04_beta, 1.18-20.04_edge)
* zlib1g: 5355-1
Revision r7057ce4045c1 (s390x; channels: 1.18-21.10_beta, edge, 1.18-21.10_edge, latest)
* zlib1g: 5355-1
Revision r7925141d471b (s390x; channels: 1.18-20.04_beta, 1.18-20.04_edge)
* zlib1g: 5355-1
Revision raf54d5dc1ee0 (ppc64le; channels: 1.18-21.10_beta, edge, 1.18-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/