-
-
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
[Security] Any action required for CVE-2015-7547? #286
Comments
We'll update it eventually. In the mean time, you can run |
Thanks |
Yes please do.
|
Until the phusion baseimage will ship a fix, we'll just upgrade the packages: phusion/baseimage-docker#286
Is the
Just asking. Is that an issue? Do anyone know which packages "won't upgrade"? |
I don't think it's a big issue. Things like kernel packages or bootloader packages (grub) won't upgrade because they try to do things that require more privileges. But I think the document is exaggerating when they say that "many packages won't upgrade" -- I have yet to encounter even one case of a package not upgrading well due to lack of privileges. I think the kernel and bootloader packages are already disabled in the Docker base images. And what that article says about upgrading applies equally to installing. If a package won't upgrade inside an unprivileged container, then it won't install either, so you would have noticed the issue long before you needed to upgrade. |
Thanks. Sounds reasonable. Another idea: I searched github for |
We've recently updated Baseimage-docker to Ubuntu 16.04. So the security update will also be released real soon now. |
Recently a security related CVE is published
https://www.kb.cert.org/vuls/id/457759
There is already an issue for docker official images
docker-library/official-images#1448
Anything required for this repo? Rebuild? Change of Dockerfiles/scripts?
The text was updated successfully, but these errors were encountered: