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 r14529303f1b3 (arm64; channels: 5.7-23.04_beta, 5.7-23.04_edge, edge, latest)
* libc-bin: 6409-1
* libc6: 6409-1
Revision r20386bab9b79 (ppc64le; channels: 5.2-22.04_edge, 5.2-22.04_beta)
* libc-bin: 6409-1
* libc6: 6409-1
Revision r63d84a4f786b (ppc64le; channels: 5.7-23.04_beta, 5.7-23.04_edge, edge, latest)
* libc-bin: 6409-1
* libc6: 6409-1
Revision r6c45c302e4ab (s390x; channels: 5.2-22.04_edge, 5.2-22.04_beta)
* libc-bin: 6409-1
* libc6: 6409-1
Revision r97faf1f1e7e8 (s390x; channels: 5.7-23.04_beta, 5.7-23.04_edge, edge, latest)
* libc-bin: 6409-1
* libc6: 6409-1
Revision rb37e34479db8 (amd64; channels: 5.2-22.04_edge, 5.2-22.04_beta)
* libc-bin: 6409-1
* libc6: 6409-1
Revision rc611531b6816 (arm64; channels: 5.2-22.04_edge, 5.2-22.04_beta)
* libc-bin: 6409-1
* libc6: 6409-1
Revision rd8afab9b83c1 (amd64; channels: 5.7-23.04_beta, 5.7-23.04_edge, edge, latest)
* libc-bin: 6409-1
* libc6: 6409-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-6409-1/