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 r2b81879918a1 (ppc64le; channels: 5.2-22.04_edge, 5.2-22.04_beta)
 * libssl3: 6663-1
 * openssl: 6663-1

Revision r3e27b253b100 (ppc64le; channels: 4.10-20.04_beta, 4.10-20.04_edge)
 * libssl1.1: 6663-1
 * openssl: 6663-1

Revision r5ae8d1fc056d (s390x; channels: 5.2-22.04_edge, 5.2-22.04_beta)
 * libssl3: 6663-1
 * openssl: 6663-1

Revision r6061a3935910 (arm64; channels: 5.2-22.04_edge, 5.2-22.04_beta)
 * libssl3: 6663-1
 * openssl: 6663-1

Revision r646eb99b6584 (s390x; channels: 4.10-20.04_beta, 4.10-20.04_edge)
 * libssl1.1: 6663-1
 * openssl: 6663-1

Revision r6e6c9d6e56da (arm64; channels: 4.10-20.04_beta, 4.10-20.04_edge)
 * libssl1.1: 6663-1
 * openssl: 6663-1

Revision r7c9a0b6a3ef5 (amd64; channels: 4.10-20.04_beta, 4.10-20.04_edge)
 * libssl1.1: 6663-1
 * openssl: 6663-1

Revision rb5a9ce0e0c76 (amd64; channels: 5.2-22.04_edge, 5.2-22.04_beta)
 * libssl3: 6663-1
 * openssl: 6663-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-6663-1/