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 r21bd0a5c860c (amd64; channels: 12-20.04_edge, 12-20.04_beta)
* gzip: 5378-1
* liblzma5: 5378-2
Revision r47eae5b465d6 (ppc64le; channels: 13-21.10_edge, edge, latest, 13-21.10_beta)
* gzip: 5378-1
* liblzma5: 5378-2
Revision r5a32363bcd3b (arm64; channels: 12-20.04_edge, 12-20.04_beta)
* gzip: 5378-1
* liblzma5: 5378-2
Revision r99a863768ce2 (ppc64le; channels: 12-20.04_edge, 12-20.04_beta)
* gzip: 5378-1
* liblzma5: 5378-2
Revision r9d7d0b99301e (s390x; channels: 12-20.04_edge, 12-20.04_beta)
* gzip: 5378-1
* liblzma5: 5378-2
Revision red0559844760 (s390x; channels: 13-21.10_edge, edge, latest, 13-21.10_beta)
* gzip: 5378-1
* liblzma5: 5378-2
Revision rfd52961d0e80 (amd64; channels: 13-21.10_edge, edge, latest, 13-21.10_beta)
* gzip: 5378-1
* liblzma5: 5378-2
Revision rff3f91676af1 (arm64; channels: 13-21.10_edge, edge, latest, 13-21.10_beta)
* gzip: 5378-1
* liblzma5: 5378-2
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-5378-1/
* https://ubuntu.com/security/notices/USN-5378-2/