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 r2d78c669aadf (arm64; channels: 2.4-20.04_beta, 2.4-20.04_edge)
* libasn1-8-heimdal: 5800-1
* libgssapi3-heimdal: 5800-1
* libhcrypto4-heimdal: 5800-1
* libheimbase1-heimdal: 5800-1
* libheimntlm0-heimdal: 5800-1
* libhx509-5-heimdal: 5800-1
* libkrb5-26-heimdal: 5800-1
* libroken18-heimdal: 5800-1
* libwind0-heimdal: 5800-1
Revision r3747b3fd77e0 (amd64; channels: 2.4-20.04_beta, 2.4-20.04_edge)
* libasn1-8-heimdal: 5800-1
* libgssapi3-heimdal: 5800-1
* libhcrypto4-heimdal: 5800-1
* libheimbase1-heimdal: 5800-1
* libheimntlm0-heimdal: 5800-1
* libhx509-5-heimdal: 5800-1
* libkrb5-26-heimdal: 5800-1
* libroken18-heimdal: 5800-1
* libwind0-heimdal: 5800-1
Revision r9b509e6bda1c (ppc64le; channels: 2.4-20.04_beta, 2.4-20.04_edge)
* libasn1-8-heimdal: 5800-1
* libgssapi3-heimdal: 5800-1
* libhcrypto4-heimdal: 5800-1
* libheimbase1-heimdal: 5800-1
* libheimntlm0-heimdal: 5800-1
* libhx509-5-heimdal: 5800-1
* libkrb5-26-heimdal: 5800-1
* libroken18-heimdal: 5800-1
* libwind0-heimdal: 5800-1
Revision re2baa3752fc0 (s390x; channels: 2.4-20.04_beta, 2.4-20.04_edge)
* libasn1-8-heimdal: 5800-1
* libgssapi3-heimdal: 5800-1
* libhcrypto4-heimdal: 5800-1
* libheimbase1-heimdal: 5800-1
* libheimntlm0-heimdal: 5800-1
* libhx509-5-heimdal: 5800-1
* libkrb5-26-heimdal: 5800-1
* libroken18-heimdal: 5800-1
* libwind0-heimdal: 5800-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-5800-1/
