ubuntu-docker-images team mailing list archive

[security-team-toolbox-bot@xxxxxxxxxxxxx]

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 r1062755d5169 (arm64; channels: 5.2-22.04_beta)
 * libcap2: 6166-1

Revision r2654e0366b8f (amd64; channels: 4.10-20.04_beta)
 * libcap2: 6166-1

Revision r28b34b1704ff (arm64; channels: 5.6-22.10_beta, 5.6-22.10_edge)
 * libcap2: 6166-1

Revision r5490e26f301d (s390x; channels: 5.2-22.04_beta)
 * libcap2: 6166-1

Revision r5e54104107cd (ppc64le; channels: 4.10-20.04_beta)
 * libcap2: 6166-1

Revision r6742a1f69f83 (ppc64le; channels: 5.6-22.10_beta, 5.6-22.10_edge)
 * libcap2: 6166-1

Revision r6e6d2fa13201 (amd64; channels: 5.6-22.10_beta, 5.6-22.10_edge)
 * libcap2: 6166-1

Revision r92dfd22e15df (arm64; channels: 4.10-20.04_beta)
 * libcap2: 6166-1

Revision rb0cd61034203 (s390x; channels: 4.10-20.04_beta)
 * libcap2: 6166-1

Revision rc01d56dc40b1 (s390x; channels: 5.6-22.10_beta, 5.6-22.10_edge)
 * libcap2: 6166-1

Revision rf7c6ed3af026 (amd64; channels: 5.2-22.04_beta)
 * libcap2: 6166-1

Revision rfbb828d97c2c (ppc64le; channels: 5.2-22.04_beta)
 * libcap2: 6166-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-6166-1/