Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

"This image has vulnerabilities" on Docker Hub #46

Closed
teohhanhui opened this issue Jun 15, 2016 · 6 comments
Closed

"This image has vulnerabilities" on Docker Hub #46

teohhanhui opened this issue Jun 15, 2016 · 6 comments
Labels

Comments

@teohhanhui
Copy link

No description provided.

@punkeel
Copy link

punkeel commented Aug 20, 2016

👍

@jmreicha
Copy link

Is there any update on this? I'm seeing this for all the tags in the nodejs repo.

@yosifkit
Copy link
Member

We have to wait for any fixes to come through the Debian packaging. Sometimes, even though there is a CVE, the Debian security team does not think the vulnerability warrants a backport (like this and this).

Even when there are fixes available, unless they are actually exploitable and foundational to many programs (like openssl), we hesitate to force a rebuild of all dependent images. On the other hand we strive to make sure exploitable vulnerabilities are fixed: see docker-library/official-images label:cve-tracker.

If we take for example buildpack-deps:jessie, of the roughly 70 CVE's listed on the ~20 different components on the Docker Hub, there are fixes now for 4 packages that covers 17 CVEs. Of those, only two are "High" severity; one for curl that "We are not aware of any exploit of this flaw." (curl.haxx.se) and one for imagemagick, which doesn't look bad enough to cause a rebuild of images.

Sometimes there are false positive on the Docker Hub list as well. Like CVE-2016-4614, CVE-2016-4615, CVE-2016-4616, CVE-2016-4619 which apply to iOS, OSX, tvOS, watchOS, and iTunes on Windows, and CVE-2016-5131 which applies when using Google Chrome.

We do periodically rebuild the base Debian and Ubuntu image on about a monthly time frame (and rebuild all dependent images), so any available fixes will naturally be installed. We just rebuilt Ubuntu today and plan to rebuild Debian next week.

@jmreicha
Copy link

Thanks for the very thorough explanation, everything you mention makes sense.

@yosifkit
Copy link
Member

@tianon
Copy link
Member

tianon commented Feb 26, 2019

See https://github.com/docker-library/faq#why-does-my-security-scanner-show-that-an-image-has-so-many-cves for where this information has been finally combined into a more complete FAQ answer.

@tianon tianon closed this as completed Feb 26, 2019
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants