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 r37cea3f74248 (ppc64le; channels: 1.5-20.04_beta, 1.5-20.04_edge)
* libssl1.1: 5328-1
* tar: 5329-1
Revision r44e66ef44245 (amd64; channels: edge, 1.6-21.10_edge, latest, 1.6-21.10_beta)
* libssl1.1: 5328-1
Revision r7ba84ae02db4 (s390x; channels: edge, 1.6-21.10_edge, latest, 1.6-21.10_beta)
* libssl1.1: 5328-1
Revision r83be594c91fe (ppc64le; channels: edge, 1.6-21.10_edge, latest, 1.6-21.10_beta)
* libssl1.1: 5328-1
Revision rc18c1834a598 (s390x; channels: 1.5-20.04_beta, 1.5-20.04_edge)
* libssl1.1: 5328-1
* tar: 5329-1
Revision rd6e184e2fe3f (arm64; channels: edge, 1.6-21.10_edge, latest, 1.6-21.10_beta)
* libssl1.1: 5328-1
Revision ref76ca7e2e01 (arm64; channels: 1.5-20.04_beta, 1.5-20.04_edge)
* libssl1.1: 5328-1
* tar: 5329-1
Revision rf0c33fa1e70f (amd64; channels: 1.5-20.04_beta, 1.5-20.04_edge)
* libssl1.1: 5328-1
* tar: 5329-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-5328-1/
* https://ubuntu.com/security/notices/USN-5329-1/
