Skip to content
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

Anchore Go Library - Vulnerabilities - Update code to allow unpinning of versions. #637

Open
srisek opened this issue Mar 7, 2024 · 3 comments

Comments

@srisek
Copy link

srisek commented Mar 7, 2024

Our org is using the Jammy base builder and base runner with the latest version in my CI tool to perform builds and got the below Critical/High security vulnerabilities identified by the scanning tool for the npm-install build pack.

  1. Go Library: github.com/anchore/syft

Impacted Layer : /layers/paketo-buildpacks_npm-install/launch-modules/exec.d/0-setup-symlinks

CVE-2022-28346
CVE-2022-28347
CVE-2022-34265
CVE-2023-31047
CVE-2021-45115
CVE-2021-45116
CVE-2022-23833
CVE-2022-36359
CVE-2022-41323

The recommended fix is to updated to version github.com/anchore/syft 0.89.0 and could see references of version 0.80.0 in the go dependencies used by the npm-install build pack.

https://github.com/paketo-buildpacks/npm-install/blob/main/go.mod#L33C2-L33C45

Can this be updated to the version – 0.89.0?

  1. Go Library: github.com/anchore/stereoscope

Impacted Layer: /layers/paketo-buildpacks_npm-install/launch-modules/exec.d/0-setup-symlinks
Installed Resource: github.com/anchore/stereoscope 0.0.0-20230412183729-8602f1afc574

CVE-2024-24579

Recommended Fix: Upgrade package github.com/anchore/stereoscope to version 0.0.1 or above.

We did notice that the underlying npm-install buildpack is using 0.0.1 in the dependency, but also getting replaced with version v0.0.0-20230412183729-8602f1afc574

https://github.com/paketo-buildpacks/npm-install/blob/main/go.mod#L159C80-L159C115

Request any guidance or help in getting these addressed with your team’s help.

@mhdawson
Copy link
Member

This is the commit in which it was pinned - 0a9a25d

But I can't seem to find any discussion of why in the related PR - #619

But it does say that there are breaking changes in the update to versions which were pinned.

Removing the pining seems to break either the build or unit tests.

@mhdawson
Copy link
Member

So it looks like what's needed is somebody to investigate/fix the problems caused by the breaking changes before we can unpin the versions./

@mhdawson mhdawson changed the title Anchore Go Library - Vulnerabilities Anchore Go Library - Vulnerabilities - Update code to allow unpinning of versions. Oct 24, 2024
@mhdawson
Copy link
Member

@srisek I know its been a long time, but if this is still on your radar, any help in figuring out what other changes are needed to go along with the unpining would help move it along.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants