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 r113ec0bdcaf4 (arm64; channels: 1.18-20.04_beta, 1.18-20.04_edge)
* libexpat1: 5320-1
Revision r3c68a08baec7 (amd64; channels: 1.18-21.10_edge, edge, 1.18-21.10_beta, latest)
* libexpat1: 5320-1
Revision r47dd69f3df06 (ppc64le; channels: 1.18-21.10_edge, edge, 1.18-21.10_beta, latest)
* libexpat1: 5320-1
Revision ra1ad809b49f2 (s390x; channels: 1.18-21.10_edge, edge, 1.18-21.10_beta, latest)
* libexpat1: 5320-1
Revision rc10e83971a21 (amd64; channels: 1.18-20.04_beta, 1.18-20.04_edge)
* libexpat1: 5320-1
Revision rd3f2bfcf9c65 (s390x; channels: 1.18-20.04_beta, 1.18-20.04_edge)
* libexpat1: 5320-1
Revision rd56d4cd1c93d (arm64; channels: 1.18-21.10_edge, edge, 1.18-21.10_beta, latest)
* libexpat1: 5320-1
Revision rfaa65958dfe6 (ppc64le; channels: 1.18-20.04_beta, 1.18-20.04_edge)
* libexpat1: 5320-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.