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 r48f4081265dd (arm64; channels: 1.18-20.04_edge, 1.18-20.04_beta)
* libtiff5: 5619-1
Revision r5461eb8a5597 (ppc64le; channels: 1.18-20.04_edge, 1.18-20.04_beta)
* libtiff5: 5619-1
Revision r70cb01fc43ed (arm64; channels: latest, edge, 1.18-22.04_beta, 1.18-22.04_edge)
* libtiff5: 5619-1
Revision r88ff5a0effcb (s390x; channels: latest, edge, 1.18-22.04_beta, 1.18-22.04_edge)
* libtiff5: 5619-1
Revision r8925627aa4a8 (amd64; channels: 1.18-20.04_edge, 1.18-20.04_beta)
* libtiff5: 5619-1
Revision r98408f11a9dc (amd64; channels: latest, edge, 1.18-22.04_beta, 1.18-22.04_edge)
* libtiff5: 5619-1
Revision rbc6cd8c64989 (ppc64le; channels: latest, edge, 1.18-22.04_beta, 1.18-22.04_edge)
* libtiff5: 5619-1
Revision re9e49bf11758 (s390x; channels: 1.18-20.04_edge, 1.18-20.04_beta)
* libtiff5: 5619-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-5619-1/