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 r0d98fc4e28b0 (amd64; channels: 1.18-22.04_beta, 1.18-22.04_edge)
* libtiff5: 5714-1
Revision r6734b2a98a73 (amd64; channels: 1.18-20.04_beta, 1.18-20.04_edge)
* libtiff5: 5714-1
Revision r6f0fea35c36a (s390x; channels: 1.18-22.04_beta, 1.18-22.04_edge)
* libtiff5: 5714-1
Revision r9f816928ae7c (ppc64le; channels: 1.18-20.04_beta, 1.18-20.04_edge)
* libtiff5: 5714-1
Revision rb4d38ff59a2c (s390x; channels: 1.18-20.04_beta, 1.18-20.04_edge)
* libtiff5: 5714-1
Revision rca49968277a1 (arm64; channels: 1.18-22.04_beta, 1.18-22.04_edge)
* libtiff5: 5714-1
Revision rf4a304376d10 (ppc64le; channels: 1.18-22.04_beta, 1.18-22.04_edge)
* libtiff5: 5714-1
Revision rf8587314a33b (arm64; channels: 1.18-20.04_beta, 1.18-20.04_edge)
* libtiff5: 5714-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-5714-1/