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 r179454ad122b (s390x; channels: latest, 1.6-22.04_beta, edge, 1.6-22.04_edge)
* zlib1g: 5570-2
Revision r1e2046876f44 (amd64; channels: latest, 1.6-22.04_beta, edge, 1.6-22.04_edge)
* zlib1g: 5570-2
Revision r3a420c17569d (arm64; channels: latest, 1.6-22.04_beta, edge, 1.6-22.04_edge)
* zlib1g: 5570-2
Revision r3b046ffad3e3 (s390x; channels: 1.5-20.04_beta, 1.5-20.04_edge)
* zlib1g: 5570-2
Revision r3fb70a8bf8aa (ppc64le; channels: latest, 1.6-22.04_beta, edge, 1.6-22.04_edge)
* zlib1g: 5570-2
Revision r5725a6e24907 (arm64; channels: 1.5-20.04_beta, 1.5-20.04_edge)
* zlib1g: 5570-2
Revision r758a13cc4d73 (ppc64le; channels: 1.5-20.04_beta, 1.5-20.04_edge)
* zlib1g: 5570-2
Revision rbc8280aad2f7 (amd64; channels: 1.5-20.04_beta, 1.5-20.04_edge)
* zlib1g: 5570-2
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-5570-2/