fix: update grype to v0.91.0 to resolve nil pointer panic#316
Conversation
Grype v0.90.0 has a bug in the Hydrater() function that causes a panic when database initialization fails. The function attempts to close a nil store pointer without checking if it's nil first. This was fixed in v0.91.0 via anchore/grype#2546. Co-authored-by: Ona <no-reply@ona.com>
Co-authored-by: Ona <no-reply@ona.com>
|
Changes in 394e89a were to fix golang ci lint errors. |
|
I didn't bump to the latest version of grype. This is because that results in a conflict with runc, which we'd need to also update, but is a bigger change than I'd like to take on in this PR. Background:
|
Description
Updates grype from v0.90.0 to v0.91.0 to fix a nil pointer dereference panic during vulnerability database hydration.
Problem
Grype v0.90.0 contains a bug where the
Hydrater()function attempts to close a database store without checking if it's nil. When database initialization fails, this causes a segmentation fault.Solution
Upgrade to grype v0.91.0, which includes the fix from anchore/grype#2546.
Changes
github.com/anchore/grypefrom v0.90.0 to v0.91.0go mod tidy