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 r0bed4e586cd5 (ppc64le; channels: 2.4-20.04_beta, 2.4-20.04_edge)
* libexpat1: 5320-1
Revision r5b277e0296de (arm64; channels: 2.4-20.04_beta, 2.4-20.04_edge)
* libexpat1: 5320-1
Revision r5eaddc8a0571 (ppc64le; channels: edge, 2.4-21.10_edge, latest, 2.4-21.10_beta)
* libexpat1: 5320-1
Revision r62c8ca563442 (amd64; channels: edge, 2.4-21.10_edge, latest, 2.4-21.10_beta)
* libexpat1: 5320-1
Revision rac7b98780f4f (amd64; channels: 2.4-20.04_beta, 2.4-20.04_edge)
* libexpat1: 5320-1
Revision rb1bfc11b9768 (s390x; channels: 2.4-20.04_beta, 2.4-20.04_edge)
* libexpat1: 5320-1
Revision re25065389ca9 (s390x; channels: edge, 2.4-21.10_edge, latest, 2.4-21.10_beta)
* libexpat1: 5320-1
Revision rff0a56f6dfeb (arm64; channels: edge, 2.4-21.10_edge, latest, 2.4-21.10_beta)
* 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.