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 r61bdc2428126 (amd64; channels: 2.4-22.04_beta, 2.4-22.04_edge)
* libapr1: 5885-1
Revision r6d6d9cc14061 (s390x; channels: 2.4-22.10_beta, edge, latest, 2.4-22.10_edge)
* libapr1: 5885-1
Revision r94ef826310c9 (ppc64le; channels: 2.4-22.10_beta, edge, latest, 2.4-22.10_edge)
* libapr1: 5885-1
Revision r9508c9234dec (amd64; channels: 2.4-22.10_beta, edge, latest, 2.4-22.10_edge)
* libapr1: 5885-1
Revision rb24156d5b846 (arm64; channels: 2.4-22.04_beta, 2.4-22.04_edge)
* libapr1: 5885-1
Revision rd7996fd4745f (s390x; channels: 2.4-22.04_beta, 2.4-22.04_edge)
* libapr1: 5885-1
Revision re1cbbb851ebc (arm64; channels: 2.4-22.10_beta, edge, latest, 2.4-22.10_edge)
* libapr1: 5885-1
Revision re8b11c413756 (ppc64le; channels: 2.4-22.04_beta, 2.4-22.04_edge)
* libapr1: 5885-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-5885-1/