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 r4ff89571ce8d (s390x; channels: 2.4-20.04_beta, 2.4-20.04_edge)
* libcurl4: 5702-1
Revision r5d81e425053b (arm64; channels: 2.4-22.04_edge, 2.4-22.04_beta)
* libcurl4: 5702-1
Revision r858f692b8284 (s390x; channels: 2.4-22.04_edge, 2.4-22.04_beta)
* libcurl4: 5702-1
Revision rc2bcff2354a5 (amd64; channels: 2.4-20.04_beta, 2.4-20.04_edge)
* libcurl4: 5702-1
Revision rcb7e4cff2961 (ppc64le; channels: 2.4-22.04_edge, 2.4-22.04_beta)
* libcurl4: 5702-1
Revision rd388ab19aee0 (arm64; channels: 2.4-20.04_beta, 2.4-20.04_edge)
* libcurl4: 5702-1
Revision re0d66871975d (amd64; channels: 2.4-22.04_edge, 2.4-22.04_beta)
* libcurl4: 5702-1
Revision rf338765fad0e (ppc64le; channels: 2.4-20.04_beta, 2.4-20.04_edge)
* libcurl4: 5702-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-5702-1/