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 r42e50fd7a3f2 (s390x; channels: 2.4-20.04_edge, 2.4-20.04_beta)
* libssl1.1: 5328-1
* tar: 5329-1
Revision r66ab861e6587 (ppc64le; channels: 2.4-20.04_edge, 2.4-20.04_beta)
* libssl1.1: 5328-1
* tar: 5329-1
Revision r80ca3d6b76cf (amd64; channels: 2.4-20.04_edge, 2.4-20.04_beta)
* libssl1.1: 5328-1
* tar: 5329-1
Revision r8c71c411c0ae (arm64; channels: 2.4-20.04_edge, 2.4-20.04_beta)
* libssl1.1: 5328-1
* tar: 5329-1
Revision ra9c7da113cc7 (ppc64le; channels: edge, 2.4-21.10_beta, 2.4-21.10_edge, latest)
* libssl1.1: 5328-1
Revision rabaeaa105b55 (arm64; channels: edge, 2.4-21.10_beta, 2.4-21.10_edge, latest)
* libssl1.1: 5328-1
Revision rdf49e9d87030 (s390x; channels: edge, 2.4-21.10_beta, 2.4-21.10_edge, latest)
* libssl1.1: 5328-1
Revision rea06d20e9d2c (amd64; channels: edge, 2.4-21.10_beta, 2.4-21.10_edge, latest)
* libssl1.1: 5328-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/
