-
Notifications
You must be signed in to change notification settings - Fork 297
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
CVE(s) found #1605
Comments
Grype output:
|
I ran grype against the docker image of pack published at docker hub, after checking the latest 'go.mod' file, I noticed some of the CVEs should be fixed with the latest dependencies update. So I built pack from the main branch, and then scan that image. As we can see 1 CVE is already fixed, the first one, but there one still open:
|
Also I think the dependencies came from the lifecycle. see this imagre And the scanning of the lifecycle The problem is the lifecycle seems to be related to the dependency with Kaniko, see |
Good catch @jjbustamante - in this case we might need to create a .grype.yaml file (as we do for the lifecycle) to exclude the ones that aren't possible to patch. This may all go away if we can update the kaniko dependencies (as was suggested here) but we are still waiting for upstream changes to be released. |
We will check this one after 0.30.0 is released |
I just built locally pack 0.30.0-RC2 and it looks fine.
|
Latest buildpacksio/pack v0.28.0 triggered CVE(s) from Grype. For further details, see: https://github.com/buildpacks/pack/actions/runs/3982774258
The text was updated successfully, but these errors were encountered: