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 r2b3fada7bd3c (arm64; channels: 1.18-21.10_edge, latest, edge, 1.18-21.10_beta)
* libxml2: 5324-1
Revision r3f109149c48e (arm64; channels: 1.18-20.04_beta, 1.18-20.04_edge)
* libxml2: 5324-1
Revision r5eaacbcc2cd6 (amd64; channels: 1.18-21.10_edge, latest, edge, 1.18-21.10_beta)
* libxml2: 5324-1
Revision r7877a6b071bb (s390x; channels: 1.18-21.10_edge, latest, edge, 1.18-21.10_beta)
* libxml2: 5324-1
Revision r8a0dad9bc454 (amd64; channels: 1.18-20.04_beta, 1.18-20.04_edge)
* libxml2: 5324-1
Revision rb263d34bc169 (s390x; channels: 1.18-20.04_beta, 1.18-20.04_edge)
* libxml2: 5324-1
Revision re5cf35ed0149 (ppc64le; channels: 1.18-21.10_edge, latest, edge, 1.18-21.10_beta)
* libxml2: 5324-1
Revision reebf044e7584 (ppc64le; channels: 1.18-20.04_beta, 1.18-20.04_edge)
* libxml2: 5324-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-5324-1/