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 r005b780a695c (s390x; channels: 2.4-22.10_beta)
* libcap2: 6166-1
Revision r120be1a31736 (amd64; channels: 2.4-22.10_beta)
* libcap2: 6166-1
Revision r17beaea313a9 (arm64; channels: 2.4-22.04_edge, 2.4-22.04_beta)
* libcap2: 6166-1
Revision r6203e98bdec2 (arm64; channels: 2.4-22.10_beta)
* libcap2: 6166-1
Revision r6e546eb110b1 (amd64; channels: 2.4-22.04_edge, 2.4-22.04_beta)
* libcap2: 6166-1
Revision ra85249dea0a8 (s390x; channels: 2.4-22.04_edge, 2.4-22.04_beta)
* libcap2: 6166-1
Revision ra9a5f14a9c0a (ppc64le; channels: 2.4-22.04_edge, 2.4-22.04_beta)
* libcap2: 6166-1
Revision rc90027c94da1 (ppc64le; channels: 2.4-22.10_beta)
* libcap2: 6166-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-6166-1/