-
Notifications
You must be signed in to change notification settings - Fork 2k
CVE-2019-15847 #1315
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
Comments
Dear Simen, Policy is clear and logical. But:
and I can see in dockerfile that this image is depends on FROM alpine:3.11 and this part of code actually installs build prerequisites. And if I am rebuilding using this Dockerfile, I am getting different gcc version: 9.3.0-r0.
And this is the right version, which has no vulnerability. So may be in docker hub, this image somehow not updated. Bashbrew process failed or cache is taken? |
Dunno... @tianon? |
On August 19, 2020 12:34:42 PM UTC, Simen Bekkhus ***@***.***> wrote:
Dunno... @tianon?
This also might be an answer. Package updated in alpine 6 days ago. https://git.alpinelinux.org/aports/commit/?h=3.11-stable&id=998910db5afb89b3f84a6c9237f4c02c164fc1c5
|
See https://github.com/docker-library/faq#why-does-my-security-scanner-show-that-an-image-has-cves, especially:
What I would suggest is asking the Alpine Linux community to make a new release of 3.11 so that downstream images can get rebuilt and include the updated packages (especially security fixes). |
@tianon |
Unfortunately, official-images builds make heavy use of "docker build" cache so as to not cause unnecessary image churn for users. So the only way to get images to rebuild is to update the base image. Which is why we rebuild all |
Wait, iss docker-node/12/alpine3.11/Dockerfile Lines 28 to 36 in 4798f99
docker-node/12/alpine3.11/Dockerfile Line 62 in 4798f99
|
the issue is with this line: docker-node/12/alpine3.11/Dockerfile Lines 7 to 8 in 4798f99
It installs:
This is a prerequisite for node to be working actually, if libstdc++ is removed, then node is not working at all. |
We could cheat to trigger a rebuild by adding a comment above those lines about why it's installed, then? Doing so would trigger an updated build for docker hub |
Unless new release is planned in near future. |
|
aprox 2 months from today. Hmm, unless alpine will release some bug fixes before. I don't know if You want to rely on Alpine or trigger rebuild manually. I would prefer rebuild, as node is dependent on libstdc++. But You decide. |
@SimenB, |
I'm not sure why you're actually hitting the install steps, as there is a pre-built binary that should be picked up for the x64 platform. The manual build step should only kick in when running on something like ARM or other chipsets |
@nschonni |
Thanks! I'm thinking it was required for running Node as it's also like this in https://github.com/nodejs/unofficial-builds/blob/master/recipes/musl/Dockerfile, but I'm not really sure |
It is actualy a mandatory requirement, without it node breaks. |
So what is the alternative to waiting for the next nodejs or alpine release? Do I just need to update gcc in my container? |
You could. But in the description of CVE-2019-15847 and made clear on the Debian security tracker, it "affects only POWER9 binaries". So it is unlikely to be relevant. Note that this CVE is "unfixed" in all stable and LTS releases of Debian and Ubuntu.
|
Hi,
Please fix CVE-2019-15847 in node:12-alpine image tag.
Thx.
The text was updated successfully, but these errors were encountered: