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 r10be55dc6fc7 (amd64; channels: 1.18-22.04_beta, 1.18-22.04_edge)
 * login: 5745-1
 * passwd: 5745-1

Revision r12bd235eb5aa (arm64; channels: 1.18-20.04_edge, 1.18-20.04_beta)
 * login: 5745-1
 * passwd: 5745-1

Revision r2b9c65404005 (s390x; channels: 1.18-20.04_edge, 1.18-20.04_beta)
 * login: 5745-1
 * passwd: 5745-1

Revision r2ddc92b94b4f (ppc64le; channels: 1.18-20.04_edge, 1.18-20.04_beta)
 * login: 5745-1
 * passwd: 5745-1

Revision r3ce5f3afd7fb (ppc64le; channels: 1.18-22.04_beta, 1.18-22.04_edge)
 * login: 5745-1
 * passwd: 5745-1

Revision ra70b7bd0e506 (amd64; channels: 1.18-20.04_edge, 1.18-20.04_beta)
 * login: 5745-1
 * passwd: 5745-1

Revision re99bd4d56558 (arm64; channels: 1.18-22.04_beta, 1.18-22.04_edge)
 * login: 5745-1
 * passwd: 5745-1

Revision rf586ed328a31 (s390x; channels: 1.18-22.04_beta, 1.18-22.04_edge)
 * login: 5745-1
 * passwd: 5745-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-5745-1/