-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CVE-2021-23840 still in recent Debian Buster based Python images #580
Comments
Looks like the recent security update just missed it docker-library/official-images#9658 But there's another PR up docker-library/official-images#9670 |
Unfortunately, docker-library/official-images#9670 is not going to have an effect, since it only changes the pip installation. That happens after the installation of python and the builds make heavy use of Docker build cache, so the earlier layers will be unchanged when the images are built. Since this likely affects more than just the
Last Debian update was docker-library/official-images#9590, so the usual 30-day cadence would still be over two weeks away. @tianon, of the three CVE's in the OpenSSL Security Advisory, |
Is it possible that the most recent builds for the Debian Buster based images were built from an outdated Debian package cache? Dockerfiles for the 3.8 and 3.9 versions were updated on Feb. 19 (c285e28, 91cbd74), but the corresponding images on Dockerhub still contain the vulbnerable
openssl 1.1.1d-0+deb10u4
.On the other hand the Debian Security Tracker lists this vulnerability as fixed with the updated
openssl 1.1.1d-0+deb10u5
being available since Feb. 17 (DSA-4855-1), i.e. two days earlier!When I build a
python:3.9-slim
image from the Dockerfile in this repo myself (today, i.e. Feb 20), I get the updated package.See also #578.
The text was updated successfully, but these errors were encountered: