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 r468059db916c (s390x; channels: latest, edge, 2.4-22.04_edge, 2.4-22.04_beta)
* libcurl4: 5587-1
Revision r77474d84d801 (ppc64le; channels: 2.4-20.04_beta, 2.4-20.04_edge)
* libcurl4: 5587-1
Revision r80ff429ab3f7 (arm64; channels: 2.4-20.04_beta, 2.4-20.04_edge)
* libcurl4: 5587-1
Revision racc5273e41d6 (amd64; channels: latest, edge, 2.4-22.04_edge, 2.4-22.04_beta)
* libcurl4: 5587-1
Revision rba64da8fbc1f (ppc64le; channels: latest, edge, 2.4-22.04_edge, 2.4-22.04_beta)
* libcurl4: 5587-1
Revision rc1f9faa0f4c3 (arm64; channels: latest, edge, 2.4-22.04_edge, 2.4-22.04_beta)
* libcurl4: 5587-1
Revision rdb0f2baa8270 (amd64; channels: 2.4-20.04_beta, 2.4-20.04_edge)
* libcurl4: 5587-1
Revision re3fae3feecb9 (s390x; channels: 2.4-20.04_beta, 2.4-20.04_edge)
* libcurl4: 5587-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-5587-1/