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 r33219a2eb90f (ppc64le; channels: edge, 6.0-21.10_beta, 6.0-21.10_edge, latest)
* libssl1.1: 5328-1
Revision r62508f4529b3 (arm64; channels: edge, 6.0-21.10_beta, 6.0-21.10_edge, latest)
* libssl1.1: 5328-1
Revision r7138c1993c7d (arm64; channels: 5.0-20.04_beta, 5.0-20.04_edge)
* tar: 5329-1
Revision ra63a3949d44c (amd64; channels: 5.0-20.04_beta, 5.0-20.04_edge)
* tar: 5329-1
Revision rabcb63d04940 (s390x; channels: 5.0-20.04_beta, 5.0-20.04_edge)
* tar: 5329-1
Revision rb363e7a007d3 (ppc64le; channels: 5.0-20.04_beta, 5.0-20.04_edge)
* tar: 5329-1
Revision rb372d35af442 (amd64; channels: edge, 6.0-21.10_beta, 6.0-21.10_edge, latest)
* libssl1.1: 5328-1
Revision re39a424f9dde (s390x; channels: edge, 6.0-21.10_beta, 6.0-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/