You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
ahaerpfer
changed the title
CVE-2021-23840 still in recent Debian Buster images
CVE-2021-23840 still in recent Debian Buster based Python images
Feb 20, 2021
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 python images, our usual path would be to rebuild the base image (debian) and then all dependent official-images would be rebuilt and benefit.
We strive to publish updated images at least monthly for Debian and Ubuntu. We also rebuild earlier if there is a critical security need, e.g. docker-library/official-images#2171. [...] These refreshed base images also means that any other image in the Official Images program that is FROM them will also be rebuilt (as described in the project README.md file).
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: