Open jacek99 opened 4 years ago
Thanks for reporting! It seems we should update our base image used by docker build. Before we update the official image, you can try to build your own and update the base image in Dockerfile we used.
Is the tool Twistlock is open source? We'd like to integrate tools into our release pipeline to do aotumatically check in the future.
Hi @XiaoningLiu Thought it's an old issue and versions are older as well but I am trying to build azurite container with 3.14.0 and I can see one critical, one high and one medium vulnerabilities in the latest scan by trivy scan. Can you please suggest what can be done as our build tool is rejecting this due to these vulnerabilities and it's critical for us to get these resolved. Security team has suggested that we raise this with official maintainer rather suppress in pipeline.
command used
trivy image --ignore-unfixed mcr.microsoft.com/azure-storage/azurite:3.14.0
Hi @skharab-anaplan, all 3 reported libraries are Azurite indirect dependencies.
The CRITIAL one for apk-tools should from the base docker image we are using. This should be auto resolved by Azurite's next docker image build and release.
The other 2 requires dependencies version bump up in package.json. Just check if you or others want to have a quick contribution?
Hi @skharab-anaplan, all 3 reported libraries are Azurite indirect dependencies.
The CRITIAL one for apk-tools should from the base docker image we are using. This should be auto resolved by Azurite's next docker image build and release.
The other 2 requires dependencies version bump up in package.json. Just check if you or others want to have a quick contribution?
I will be more than happy to do that. Let me create PR for that. Is there are docs that I need to follow?
We tried importing the Docker Azurite image, but our security tool (Twistlock) scans it for vulnerabilities and rejected the image:
Pls correct critical vulnerabilities and issues in the image