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 r06e26ebad6f2 (amd64; channels: 12-20.04_edge, 12-20.04_beta)
* libsepol1: 5391-1
Revision r14ab495fc5f6 (ppc64le; channels: 13-21.10_edge, 13-21.10_beta)
* libsepol1: 5391-1
Revision r2212b8df1e1f (arm64; channels: 12-20.04_edge, 12-20.04_beta)
* libsepol1: 5391-1
Revision r49f2b7e932e3 (s390x; channels: 12-20.04_edge, 12-20.04_beta)
* libsepol1: 5391-1
Revision r4bdfc9ebd77d (amd64; channels: 13-21.10_edge, 13-21.10_beta)
* libsepol1: 5391-1
Revision r74dc69e0811f (s390x; channels: 13-21.10_edge, 13-21.10_beta)
* libsepol1: 5391-1
Revision ra6957c24935b (ppc64le; channels: 12-20.04_edge, 12-20.04_beta)
* libsepol1: 5391-1
Revision rb3e80f5032ad (arm64; channels: 13-21.10_edge, 13-21.10_beta)
* libsepol1: 5391-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-5391-1/