-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Vulnerabilities in git <2.17.1 #772
Comments
I would check your docker setup, specifically the networking, because For instance, running this locally worked for me: docker run -it --rm node:10.3.0 bash -c "/usr/bin/apt-get update && /usr/bin/apt-get install git -y" |
@chorrell Thank you for your reply. apt-get update # This one works ok
apt-get install software-properties-common # To get the add-apt-repository command
add-apt-repository ppa:git-core/ppa
apt-get update # This is the one failing. It fails because it tries fetch information from a mirror that doesn't exist. Regardless, since that vulnerability has been publicly reported by NPM, I think it would be reasonable to expect this image to be built with a version of git that does not contain any known vulnerabilities. I'm wondering what you all think about it? |
Ah, ok. I guess they don't provide a ppa for debian jessie. One thing to note though is that Debian has released a security update to address the submodule issue for git 2.1.4 via the
Most distros release security patches for an existing version so in the case of Debian jessie you don't need to upgrade to 2.17.1. The following will update git to the patched
Git is installed in the |
Ah, thank you for those references. I tried and confirmed that Also, thank you for the details about upstream. I guess it answers my question, so I'm going to close this issue 🙂 |
NPM has reported being affected by a vulnerability in git's submodules and advised to run
npm
with git >= 2.17.1.The
node:10.3.0
image has git v2.1.4 installed on it.I tried to install the latest version of git in my own
Dockerfile
, following the instructions given by git for the Debian distros, but it doesn't seem to work (I get a 404 HTTP status when runningapt-get update
; it seems there is no support for Debian on that mirror? 😕)As users of this image, are there any recommended actions we can take to assure the security of what we run in containers based on this image?
The text was updated successfully, but these errors were encountered: