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 r056c7baf51d5 (amd64; channels: latest, 2.4-23.04_edge, edge, 2.4-23.04_beta)
* libssl3: 6450-1
Revision r48fbc5183b56 (s390x; channels: latest, 2.4-23.04_edge, edge, 2.4-23.04_beta)
* libssl3: 6450-1
Revision r60db635324c6 (ppc64le; channels: 2.4-22.04_beta, 2.4-22.04_edge)
* libssl3: 6450-1
Revision r67a80889cbfc (amd64; channels: 2.4-22.04_beta, 2.4-22.04_edge)
* libssl3: 6450-1
Revision rd7a356fe9aed (ppc64le; channels: latest, 2.4-23.04_edge, edge, 2.4-23.04_beta)
* libssl3: 6450-1
Revision re46ad319e5ed (s390x; channels: 2.4-22.04_beta, 2.4-22.04_edge)
* libssl3: 6450-1
Revision re56f3dab898d (arm64; channels: latest, 2.4-23.04_edge, edge, 2.4-23.04_beta)
* libssl3: 6450-1
Revision rf19d435e768f (arm64; channels: 2.4-22.04_beta, 2.4-22.04_edge)
* libssl3: 6450-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-6450-1/